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

Re: cmd line stuff (was: CVS update: ...)

From: Matthew Braithwaite <matt_at_braithwaite.net>
Date: 2000-10-19 00:44:31 CEST

On Wed, 18 Oct 2000 07:35:38 -0700, Bruce Korb <bkorb@sco.COM> said:
> Matthew Braithwaite wrote:
>> CVS="cvs -q -d something"
>> in a shell script.
>> Of course, there's nothing in your suggestion that precludes being able to
>> put options in either place.
> I don't think so:
> export SVN_QUIET
> svn mumble <option-list>
> should work just fine :-), as would putting the same info
> in your ~/.svnrc file.

<testily>Just because it is *possible* to do it that way does not mean
that it is convenient in all cases. Adding options to $SVN is

Being able to modify the behavior of a command by aliasing it or
sticking options at the end is a standard and useful thing, and
there's no reason we should break it. People who write scripts will
curse us if they have to say

        SVN_OPTIONS="-foo -bar -baz"

        svn subcommand1 $SVN_OPTIONS args

        svn subcommand2 $SVN_OPTIONS args

Plus, a shell script does not have the option of modifying ~/.svnrc to
suit itself.

This is nothing that Jonathan Shapiro and Greg Stein havn't already
said before, of course.

: <20001018135406.E26804@lyra.org>

but since Karl seems to be counting votes, I wanted to throw mine
in. :-)
Received on Sat Oct 21 14:36:11 2006

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