Re: Branch causes missing revs and errors merging

On Feb 20, 2007, at 10:07, Phillip Susi wrote:

> Frodak Baksik wrote:
>
>> Actually it won't because as according to the documentation the copy
>> command does not use peg revisions. Here, I'll quote it for you:
>> From the book:
>> A second, more targeted strategy is not to use svn merge at all, but
>> rather the svn copy command.
>> Simply copy the exact revision and path "coordinate pair" from the
>> repository to your
>> working copy:
>> $ svn copy --revision 807 \
>> http://svn.example.com/repos/calc/trunk/real.c ./real.c
>> $ svn status
>> A + real.c
>
> Oh my, that is really messed up. The copy command then, uses the
> common parameter in a manner that is inconsistent with the way that
> common parameter is used with all other svn commands. The other
> commands resolve the name in the peg revision, then track the
> history back to the revision specified in -r. Copy interprets -r
> AS the peg revision. This inconsistency is poor behavior.

And I believe this inconsistency has already been fixed for
Subversion 1.5.0:

http://subversion.tigris.org/issues/show_bug.cgi?id=2546

-- 
To reply to the mailing list, please use your mailer's Reply To All  
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org