On Mar 6, 4:04, SL Baur wrote:
>Andreas Jaeger <aj(a)suse.de> writes in xemacs-beta(a)xemacs.org:
>
>> You should be able to move the file in the repository itself. This
>> keeps the history.
>
>Except that you will lose the ability to check out previous versions.
I missed the start of the thread, so I'm not sure what it's exactly
about, but as far as moving a file in the repository is concerned
Steve is right. Not being able to check out previous versions defies
the whole purpose of version control. And, in addition, everybody who
had the file checked out in its original incarnation will run into a
CVS error the next time they do a cvs update. CVS will abort because
there's an entry in people's CVS/Entries file that doesn't exist in the
repository. They will have to manually edit their CVS/Entries files.
This includes everybody out there who checked out the repository
anonymously as well.
If you want to do this you should copy, not move, the file in the
repository. Then you can rm the original file in your working tree
and cvs remove it in the usual way. You will still have an anomaly
in that 'cvs log' and 'cvs status -v' on the (new) file will indicate
that the file has a history under its new name, which is not true.
It will also be checked out if you try to check out an old version,
this can create trouble or at least make it a bit messy. To avoid
this you should use 'cvs admin' to delete all symbolic tags for the
renamed/moved file. You will still have the history but not the
tags, which may or may not make the history less useful. If you
don't do this then you're changing the history..
-Tor