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

Re: Auto-subst of repository roots (was Re: svn diff branch woprking copy against mainline?)

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2005-11-03 04:19:13 CET

Branko Čibej wrote:
> Now that we do have it, this gets a big +1 from me.
> Now let's decide about the colour of this bikeshed... I don't like
> vermilion with pink spots; in
> svn diff +/branches/foo +/trunk
> the + doesn't seem obvious enough.

Only because you're not used to it, I suspect.

> We can't use two leading slashes,
> because that could be a valid UNC path on Windows. We can't use #,
> because that's a shell meta-character. How about one of:
> svn diff ++/branches/foo ++/trunk
> svn diff %/branches/foo %/trunk
> svn diff %%/branches/foo %%/trunk
> svn diff @/branches/foo @/trunk
> svn diff @@/branches/foo @@/trunk
> I'm leaning towards % because it's somewhat mnemonic, being a URL escape

Unfortunately it's a Windows shell meta-character (for environment variables
etc., a bit like "$" in Unix).

> I think @ would be too easy to confuse with the peg-rev syntax.

Maybe, though it never appears at the beginning in that syntax and always does
in this.

> I don't think using a two-char prefix buys us much.

Huh? A few lines above, you said "how about" "++" after saying "+" didn't seem
obvious enough. But I agree a two-char prefix doesn't buy us much.

Of course, the syntax doesn't have to be a prefix string. It could, for
example, be parsed like an option, e.g. "--in-repo /trunk/foo", or implied by
the command, e.g. "svn repo-diff /trunk/foo /branches/foo".

- Julian

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 3 04:20:10 2005

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