On Sat, 2004-01-10 at 14:17, C. Michael Pilato wrote:
> Alex Besogonov <cyberax@scb.udsu.ru> writes:
<snip>
> Well, duh, that's what 'revert' does. But what does that have to do
> with CVS? If your colleague expected SVN to be like CVS, he would
> have never used the 'revert' command at all, because CVS doesn't have
> such a command.
>
cvs update -C essentially gives you this behavior for files that are in
the repository and workarea and saves your original modifications as
.#filename.baserev as pointed out by ghudson in another response.
I know I have used this 'feature' of CVS after making tons of changes to
debug a problem, finding the problem, and wanting to start the fix from
a pristine state with the modified files as a reference. Since I know
the files are there, I take them for granted and will do an update -C to
start from 'scratch' and merge the changes that I know are the actual
fix into the pristine file to resume testing.
> Sounds to me like "safe mode" is an option that one configures in
> one's own head, probably near that other famous option: "look before
> you leap."
>
This is a valid point and there are work arounds to the behavior
described above (like doing an svn status, look for modified files, and
copy them somewhere before doing a revert).
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jan 11 15:24:45 2004