Ben,
My mistake was reading "move=copy+delete" and thinking "move=make a
physical copy, add it to the repository, and then delete the original".
I didn't stop to think that the "copy" operation has more semantics than
a simple "add an identical file to the repository"---it apparently
remembers history, too.
I've been letting my IDE (Eclipse) move files, then I would do a manual
"add" and "delete" in the repository. I was using no Subversion "copy"
or equivalent (e.g. "move"), which broke history changes.
Thanks for the clarification. Now when that Subversion Eclipse plugin is
released, I'll be in good shape.
Garret
Ben Collins-Sussman wrote:
> Garret Wilson <garret@globalmentor.com> writes:
>
>
>>1. I realize there's a bug in the new
>>com/company/generic/BuildingBlock.java , but I can't revert to a
>>previous version, because that file has no previous version.
>
>
> Why can't you revert to a previous version of the file?
>
> 1. Run 'svn log' on the file, which *does* follow history back through
> the copy. Locate the (oldrev, oldpath) of the original file that
> you want to revert to.
>
> 2. svn merge newURL@HEAD oldURL@oldREV BuildingBlock.java
>
> This makes your working copy look exactly like the old version of
> BuildingBlock.java located at (oldrev, oldpath).
>
> 3. svn commit
>
>
> ---------------------------------------------------------------------
> 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 Fri Mar 7 18:33:37 2003