[flymine-dev] Code split
Matthew Wakeling
flymine-dev@flymine.org
Mon, 29 Mar 2004 22:08:50 +0100 (BST)
> >I trust that we will be using CVS changes that preserve the history of the
> >repository correctly.
> >
> The history probably but AFAIK the name of the files will be changed as
> the classnames
> will change. So dealing with a non-checked file after that will mean:
> - Identify the right directory/repository then The File
> - Check the history
> - (Probably) check it out
> - Diff/Patch the new file
> - Committing the change...
What I mean is: will one be able to call
"cvs update -D <some date in the past>" and get a valid working directory?
This will involve at least
1. Copying file from old location to new
2. Modifying the file to make it work again
3. Removing the old file
4. CVS removing the old file
5. CVS adding the new file
6. CVS committing the whole lot
Alternatively, stages 1 and 4 can be replaced with a cvsmove operation if
you really wish, but that is messy and unreliable.
Matthew
--
Note: some countries impose serious penalties for a conspiracy to overthrow
the political system. THIS DOES NOT FIX THE VULNERABILITY.