Seeking initial reactions: Moving setup from CVS to

[Reini Urban]

Benjamin Riefenstahl schrieb:
> Reini Urban <rurban@x-ray.at> writes:
>>So that you usually ssh to the cvs repo, move it there physically,
>>and update your local cvs copy then.
> 
> Don't you want to do a (physical) *copy* and than a cvs del?  That
> way, you can still checkout older versions, while if you do a physical
> *move*, you loose that.

hmm, that's a matter of policies:

the revisions are kept solely in the ,v file.
moving that will not let you loose anything. just the local CVS/Entries 
file has be updated, which is done automatically on the next cvs up.

with copy and cvs rm the server ,v timestamp will get updated, which 
does no harm to the local checkout, since cvs up will check that the 
file didn't exist anyway.
but if you do a physical copy and another local cvs client user forgets 
to cvs rm the old file, he will get into troubles, having duplicate files.
you can do a cvs rtag on the stale old file to branch it away from HEAD.

but the canonical solution is to move it physically, also recommended in 
cederquist, if I remember correctly. and better is to use mcvs which 
keeps the cvs directory history on top of cvs. (another MCVS control dir 
besides the CVS dir)

BTW: it's called cvs rm (as alias for cvs remove), not cvs del.
$ cvs del
Unknown command: `del'
$ cvs --help-commands
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/