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

Re: Peg Revision Syntax

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: 2007-01-03 15:57:05 CET

Ben Collins-Sussman wrote:
> Actually, it's already documented in the svnbook:
>
> http://svnbook.red-bean.com/nightly/en/svn.advanced.pegrevs.html
>
> Notice the sidebar text there: "Remember that even when you don't
> explicitly supply a peg-revision, it's still present. It defaults to
> BASE for working copy items, and to HEAD for URLs."
>
> On 1/3/07, Giovanni Bajo <rasky@develer.com> wrote:
>> Ben Collins-Sussman wrote:
>>
>> > Let me generalize: my understanding is that for *any* command:
>> >
>> > * URLs pegrevs default to HEAD, unless specified by @N
>> > * wc-path pegrevs default to BASE, unless specified by @N
>> > * operational revs default to pegrev, unless specified by -rN
>>
>> This has been discussed in the past:
>> http://svn.haxx.se/dev/archive-2005-11/1303.shtml
>>
>> I would like if it could be eventually set in stone and documented (in
>> the FAQ
>> maybe). I personally value more consistency among different svn commands
>> rather than endless debates on the "best" defaults :)

Thanks for the pointers. Given this information, where should the
defaulting should occur? For 'svn cat' we do it in libsvn_client,
whereas for 'svn log' we do it in the client application itself. It
doesn't appear to be happening in any single location.

Once we decide on the right layer to default, I'll just move all the
defaulting behavior there, write a helper function and call it good.

-Hyrum

Received on Wed Jan 3 15:58:11 2007

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