[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: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2004-11-02 18:43:07 CET

Greg Hudson wrote:
> On Tue, 2004-11-02 at 08:50, Julian Foad wrote:
>>Objection: I don't think you can change the meaning of existing commands before
>>version 2.
>
> You mean, like we changed the meaning of "svn diff -rN filename" in svn
> 1.1 when we added history-tracking?
>
> The rule you state should be taken with a grain of salt. There's no

That's OK by me if others agree.

In that case, please could you state the proposal a bit more completely, say as
a patch to "svn help diff" and "svn help merge"?

The current help for "diff" isn't complete:

> diff (di): Display the differences between two paths.
> usage: 1. diff [-r N[:M]] [TARGET[@REV]...]
> 2. diff [-r N[:M]] --old=OLD-TGT[@OLDREV] [--new=NEW-TGT[@NEWREV]] \
> [PATH...]
> 3. diff OLD-URL[@OLDREV] NEW-URL[@NEWREV]
>
> 1. Display the changes made to TARGETs as they are seen in REV between
> two revisions. TARGETs may be working copy paths or URLs.
>
> N defaults to BASE if any TARGET is a working copy path, otherwise it
> must be specified. M defaults to the current working version if any
> TARGET is a working copy path, otherwise it defaults to HEAD.

This doesn't say what PEG defaults to.

Is this part of your proposal:

   PEG defaults to the current working version if any TARGET is a working copy
path, otherwise it defaults to HEAD.
   M defaults to PEG.

?

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 2 18:43:30 2004

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