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

Re: Re: Bug: svn:externals property not working correctly with -r option

From: Konstantin Kolinko <knst.kolinko_at_gmail.com>
Date: Fri, 30 Sep 2011 13:45:15 +0400

2011/9/30 Paul van der Hulst <paul_at_piak.nl>:
> Hello,
>
> I ran into the same problem. Thanks for the fix
>
> In my opinion the peg method guarantees that you get exactly the original state, since the revision is resolved first, then the specific path which will exist even if the path is deleted in a later revision. What are the advantages of -r over 'peg revision' method?
>
> I fixed my problem by using only peg instead of -r. Should I use both -r and peg?
>
> I would like to suggest to add the difference to the documentation.
> Currently (1.6.16), in section 4.18.1 of the help the main method to get a revision is the -r switch. peg is mentioned all the way at the bottom of the paragraph, after the recommendation to use specific revisions. It does not describe what peg is (I searched for peg, the only hit is in 4.18.1)
>

In the old syntax (name options URL) the "-r" means peg revision.

In the "new" svn 1.5+ syntax (options URL_at_rev name) the "-r" means
operative revision and peg revision can be specified as @number after
the URL.

The operative revision (if not specified) defaults to be the same as
operative one, so using just the "@number" is enough to pin you to the
specific revision of your external.

Docs:
http://svnbook.red-bean.com/en/1.6/svn.advanced.externals.html
http://svnbook.red-bean.com/en/1.6/svn.advanced.pegrevs.html

Best regards,
Konstantin Kolinko

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2848269

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-09-30 11:45:19 CEST

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

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