On Sep 13, 2005, at 18:23, Mike Linda wrote:
> On Monday 12 September 2005 21:00, Ben Collins-Sussman wrote:
>> If you type
>> svn checkout -rX URL
>> That's equivalent to typing
>> svn checkout -rX URL@HEAD
>> But if URL@HEAD doesn't exist, you get the error you're seeing.
>> What you want to type is
>> svn checkout URL@X
> First, let me say that I understand (now) the need for @PEGREV for
> where objects are renamed and moved around, yet still present in
> some form
> in HEAD. Considering and example "svn co -rX URL@Y" (where X and Y
> different) makes sense, especially when the object had one (perhaps
> known) name in revision Y and a different (perhaps obscure) name in
> revision X -- so Subversion traces back from Y, through the rename,
> to X.
> Then it makes sense for "svn co -rX URL" to be same as "svn co -rX
> URL@HEAD". OK, so far so good.
> But... It seems to me that Subversion could be just a little
> smarter for
> cases where the object cannot be found in HEAD. Instead of raising an
> error condition, could Subversion go one step further and try
> looking only
> at version X (given "svn co -rX URL")? This is a case where there
> is no
> ambiguity and so no additional information is necessary.
> Obviously, there
> is a cost/benefit consideration, but I suspect many users migrating
> CVS would run into this (since "-rX" was all-mighty in CVS).
The only harm I can see is that users will be that much more confused
when they finally reach the case where they need peg revisions. ("But
it always worked without that before...")
But judging from the number of practically identical questions on the
list in the past month or two, it does seem like a whole lotta people
don't "get" peg revisions. I guess they get it well enough once
they're referred to the correct section in The Book, but either
they're not understanding the purpose of per revisions when they
initially read about them in The Book, or they don't even read that
section before asking.
I have yet to need to "go back in time" like this with our
repository, and I fully expect, when that time comes, that I too will
forget about peg revisions.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Sep 18 04:34:52 2005