[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Help explain peg revisions

From: Scott Palmer <scott.palmer_at_2connected.org>
Date: 2006-03-16 18:13:45 CET

On 16-Mar-06, at 12:00 PM, Phillip Susi wrote:

> Scott Palmer wrote:
>> So now I see a contradiction or misunderstanding all within the
>> same post, by someone that was attempting to clarify :)
>> You imply above that the two operations are equivalent, that they
>> both get rev 5 of the url so long as the path didn't change.
>> Then at the end of your response you claim that it will check out
>> the HEAD revision.
>> You can see how one might get confused trying to follow this:
> I'm not sure why you are confused here. If you do NOT specify
> otherwise, the default is the HEAD revision. The above statement
> is discussing a use case where you DO specify a revision ( in this
> case, 5 ).

I think you need to re-read the whole thread... your statements
effectively boiled done to indicating that :

svn checkout url@5
svn -r5 url
svn -rHEAD url@5

all did the same thing. Thus the contradiction.

My claim was that I though it made sense that

svn checkout url@5
svn -rHEAD url@5

would be the same. Since the default is to get the HEAD revision and
the purpose of the peg revision syntax was simply to refer to a path
that may not have the same name at the HEAD revision. But the
original claim that led to my first message was that the peg revision
syntax does more than specify the revision of the *namespace* to
use, it also implied that you wanted to checkout that same revision
of the content. I wanted to know which was true, if this was clearly
documented somewhere, etc. I find it confusing.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 16 18:15:14 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.