Mail Archives: djgpp-workers/2002/11/29/15:07:48
> > But that way loses the version history, compared with moving the ,v
> > files. How about a copy to the new place, followed by a cvs remove
> > of the old?
>
> If you do that, it still corrupts old tags because then you get extra
> files you shouldn't get. add/remove is the least bad of the many bad
> solutions to this problem. Besides, the file in the new location
> should *not* have a history *there*. Copying the history of the
> deleted file is misleading.
>
> Note that your initial add should include a note as to where you're
> moving from, of course, and you can still "cvs log" a removed file
> too.
In this case it doesn't make any difference (on the old tags) because
snprintf doesn't have any (other than HEAD) since it's never been
in a release.
For snprintf() the history isn't very interesting anyway (copyright
changes).
In general I prefer to use the standard cvs tools (delete it from the
old place, add it to the new place, reference old location if
someone wants to look at history) instead of playing games in the
repository directly. The cvs documentation talks about the pros and
cons of each way of moving.
In this case (and probably everything we would want to move) there's
no huge reason to do anything special.
I wouldn't be suprised with new directories it might not be best to
nuke our old trees and do a clean checkout, however, when this is all
done ...
- Raw text -