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

Re: svn commit: r1131442 - /subversion/trunk/tools/client-side/svnmucc/svnmucc.c

From: Stefan Sperling <stsp_at_elego.de>
Date: Mon, 6 Jun 2011 11:59:48 +0200

On Mon, Jun 06, 2011 at 10:17:01AM +0100, Julian Foad wrote:
> FWIW the original reasoning is in Karl's comment in parse_one_rev():
> /* Allow any number of 'r's to prefix a revision number, because
> that way if a script pastes svn output into another svn command
> (like "svn log -r${REV_COPIED_FROM_OUTPUT}"), it'll Just Work,
> even when compounded.
> I guess that means "even if one script, when given 'r123' as input, were
> to print 'rr123' as output, then we could still pass in that output as
> '-r rr123' and it would still work".
> It seems bogus (unnecessary) to me.

I use this feature regularly when copy-pasting revnums from log
messages, the #svn-dev channel, email, viewvc, etc. into the command
line. Maybe depending on how I move the mouse and the 'r' becomes
part of the paste buffer or maybe it doesn't. Some of these consider
'r' part of the "word" when I double click the revnum to mark it
for copy-pasting. Some don't. For some the double-click doesn't work.

It is really convenient to just type -r into the terminal and then
paste the number knowing that it will just work for all these cases.

I think the case Karl meant was there a script gets 123 as input
and outputs r123?
Received on 2011-06-06 12:00:31 CEST

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.