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

RE: Re: Proposed New Feature (SVNROOT)

From: Tom Browder <tom3_at_fwb.asi.srs.com>
Date: 2004-03-17 15:23:36 CET

-----Original Message-----
From: Max Bowsher [mailto:maxb@ukf.net]
Sent: Wednesday, March 17, 2004 8:08 AM
Subject: [work] Re: Proposed New Feature (SVNROOT)

Max, thanks for your comments:

> It is good idea to keep email threads to a single concept. It makes the
>discussion far easier to follow.

Will do.

> My disagreement with a SVNROOT env-var is that if you do work on more than
> one repository, you end up having to remember what the env-var is
> currently set to,

echo $SVNROOT

> and most of the time end up overriding it on the command line anyway.

That's OK, too (no change from current usage).

> Also, checkout and import are rarely used operations (for me - do you use
> them regularly in your pattern of work?)

Yes, and usually in the same repository.

> and adding complexity to slightly shorten these commands seems like
> unnecessary code.

That's what programs are for: ease the user's job.

> Any discussion of command line simplification methods should include "svn
> switch" and "svn merge" - both of which could benefit in usability from a
> way to implicitly refer to the root of the repository of the working copy
> they are running in.

That bolsters the argument in favor of such a feature.

Tom Browder

Max.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 17 15:23:19 2004

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.