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

Re: Revision 2 [was Re: [PATCH] Fix for Issue #1093 (pre-release)]

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2003-10-29 17:38:25 CET

Shlomi Fish <shlomif@vipe.technion.ac.il> writes:

> I suppose. I have some understanding of it, but don't know if it's the
> same as yours.
> As for the UI I suggest having a --base-rev REVISION flag to specify "X"
> here. I'll go with it for the while, as we can easily change it later.

Nah, that would just complicate things further. My suggestions:

1. Make the --revision (-r) option *always* talk about the operative
   revision range. That means no more 'svn foo -rM:N path1 path2' as
   an alias for 'svn foo path1@M path2@N' (thankfully... what a
   stupid overloading of a concept that was...)

2. Make the '@' syntax always talk about the "peg" revision.

3. The peg revision must always be greater than (younger than) the
   youngest revision in the operative range.

The "peg" revision is the one that is auto-populated in various
commands with things like 'BASE' or 'WORK' or 'HEAD'. So things like:

   svn diff -rM:N wcpath
   svn diff -rM:N repos-url

would do what you expect because under the hood it gets translated to

   svn diff -rM:N wcpath@BASE
   svn diff -rM:N repos-url@HEAD

This gives you tons of flexibility. Say you want to see the diffs
between revision 19 and 30 of a path that has been replaced by
something else in HEAD of the repository. Well, you know the thing
you want existed in revision 30, and you don't want to pick the
history line that exists in HEAD, so you do:

   svn diff -r19:30 repos-url@30

If you wanted the history of the thing now in HEAD between those two
revisions, you could omit the '@30'.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 29 17:39:35 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.