On Wed, 9 Mar 2005, Ben Collins-Sussman wrote:
>
> On Mar 9, 2005, at 12:15 PM, Daniel Berlin wrote:
>>
>> I believe this because that is what i believe most users expect (in fact,
>> i only noticed all of this because 3 different ex-cvs users brought it to
>> my attention)
>> I will simply note that I still find it completely unintuitiveand will
>> spend years trying to get users to use one syntax over the other because
>> it is so much faster and less load on the server :)
>>
>
> The whole peg-revision feature is new, and is the result of svn users
> complaining that commands don't follow renames.
>
> For example, people would run
>
> svn cat -rX foo.c
>
> And get errors about foo.c not existing in rX, when in fact it *did* exist,
> but in a different location. We especially got complaints about 'svn diff'
> not following renames.
>
> So what you're seeing here is a widespread consistent behavior across all
> commands:
>
> svn command -rX path
>
> 1. go to path@HEAD
> 2. trace rename history back to rX
> 3. use that (possibly different) location in rX
>
> It just so happens that in the case of 'svn co -rX URL', this new syntax and
> behavior is contradicting an equally valid interpretation of what to expect.
> :-/
Yes.
i can also see how it's very useful for other commands, and doesn't
really conflict with existing behavior there.
>
> Is this tricky to explain to users?
Yes, but i can do it by using REALLY LARGE LETTERING AND ALL CAPITAL
LETTERS.
CVS people tend not to use peg revisions, so they don't understand that
their is a significant difference in the commands i originally mentioned.
They tend to think of files as revisioned, instead of trees, until they've
used subversion for a while.
> It's not yet documented in the book,
> though I plan to fix that.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 9 20:00:52 2005