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

Re: [Issue 1351] New - svn -r 939 log vs. svn -r 939 diff inconsistency

From: William Uther <willu_at_cse.unsw.edu.au>
Date: 2003-06-08 06:46:51 CEST

On Sunday, June 8, 2003, at 04:50 AM, kfogel@collab.net wrote:

> Chris Stork <cstork@ics.uci.edu> writes:
>> I have a better suggestion:
>>
>> Define -rN: to mean -rN:WC
>> (and symmetrically -r:N to mean -rWC:N).
>>
>> (This is even a little intuitive ;) since there is no real revision
>> number that would correspond to the working copy.)
>>
>> Then Olaf gets his beef (i.e. choosing a consistent default) by
>> defining
>>
>> svn diff -rN
>>
>> to refer only to the N-1:N changes and
>>
>> svn diff -rN:
>>
>> would be the new syntax for the old semantics.
>
> Or, define some new revision keywords:
>
> svn foo -rBEFORE:N
> svn foo -rAFTER:N
> svn foo -rN:BEFORE
> svn foo -rN:AFTER
>
> to take care of N-1 and N+1, and
>
> svn foo -rWORK:N
> svn foo -rN:WORK
>
> to mean the working file. (I'm not volunteering for this, just
> pointing out that we're free to add keywords -- and probably should,
> even if we change the defaults).

If you were to paint the bikeshed in that pattern, how about using
these colours:

BEFORE doesn't refer to N-1, but rather the oldest revision before N
that is different to N in any of the supplied URLs/paths. Similarly
for AFTER.

Cheers,

Will :-}

--
Dr William Uther                            National ICT Australia
Phone: +61 2 9385 6926             School of Computer Science and 
Engineering
Email: willu@cse.unsw.edu.au             University of New South Wales
Jabber: willu@jabber.cse.unsw.edu.au          Sydney, Australia
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 8 06:48:42 2003

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

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