RE: CVS File Move

[Paul Sander]

You are correct, but technically speaking, no historical information is
lost, because the commit comment is stored on the dead revision created
when the removal is committed.  Presumably, the user remembers to make a
descriptive comment.

However, the history of the file becomes disjointed and it becomes hard
to figure out everything that has happened to the file trans-move.

--- Forwarded mail from address@hidden

Assumming that is true then no historical information is preserved. That
is to say you cannot move a file and its history without tinkering
directly with the repository. It does not matter if you wait to commit
or commit the remove and then commit the add, the result is the same?

-----Original Message-----
From: Paul Sander [mailto:address@hidden
Sent: Monday, October 06, 2003 1:01 PM
To: Rod Macpherson; address@hidden
Subject: Re: CVS File Move

CVS never assumes you want to "move" the file.  In this case, it assumes
you want to remove a file from one place and add a new file in a
different place, because that's what you told it you want to do.

The only association made between the two files is in the user's mind
and maybe in comments stored in the source code or in the revision logs.
This is true even if both actions are processed by the same commit.

--- Forwarded mail from address@hidden

To clarify the movement of files, when you remove a file X from module
/foo then add file X to module /bar CVS will assume you meant to move
the file provided you did not commit. In general I do not want CVS to
assume a relationship between a file X that was removed and a file X
that is later added in a new location. That assumption is only made when
CVS has a pending remove of a file with the same name. Is that correct?

--- End of forwarded message from address@hidden

--- End of forwarded message from address@hidden