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

Re: Should all sub-commands accept a peg-revision?

From: Josh Pieper <jjp_at_pobox.com>
Date: 2004-11-07 17:40:13 CET

C. Michael Pilato wrote:
> Okay, so, actually, I could probably be convinced that if there was a
> rule *across ALL subcommands* whereby a -r[X:]Y was present, and there
> was not an explicit peg revision noted, that the default peg revision
> changes to Y instead of HEAD or WORKING. That kind of one-line
> exception that is universal in its application is soooooooooo much
> more acceptable to me than per-subcommand exceptions.

Actually, the proposed exception was that if a peg reivision was
present, but the end destination revision was not, then the end
destination revision would default to the peg revision. That would
allow you to do things like:

svn diff -rOLD_REV URL@NEW_REV

Where the diff generated would be from OLD_REV to NEW_REV. Currently
to get that behavior you need to specify:

svn diff -rOLD_REV:NEW_REV URL@NEW_REV

This would be the same across all commands that accept a revision
range, so consistency would not be a problem.

-Josh

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 7 17:40:39 2004

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