[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: Daniel Berlin <dberlin_at_dberlin.org>
Date: 2005-11-03 14:43:18 CET

On Thu, 2005-11-03 at 11:47 +0100, Peter N. Lundblad wrote:
> On Wed, 2 Nov 2005, Daniel Berlin wrote:
>
> > On Thu, 2005-11-03 at 15:40 +1100, Peter McNab wrote:
> > > Daniel Berlin wrote:
> > >
> > > >Uh, right now, to diff the gcc 4.0 branch against a working copy file,
> > > >one has to type
> > > >svn diff
> > > >--old=svn+ssh://gcc.gnu.org/svn/gcc/branches/gcc-4_0-branch/gcc/file.c
> > > >--new file.c
> > > >
> > > >
> > >
> > > >That is all my users want. To not have to type twice or three times as
> > > >much text as they did in cvs just to do diffs
> > > >
> > > >
> > > So is there not an equivalent in *nix to the MS world where (and don't
> > > impeach me if the syntax isn't perfect)
> > > one would quickly learn to type something like
> > >
> >
> > As i explained later on, this would require roughly 16 environment
> > variables to mainly express something subversion already knows, and
> > worked fine without 16 environment variables in cvs (and perforce,
> > monotone, bitkeeper, etc)
> >
> Daniel, I'm +1 on this feature (it has been discussed before). But why
> would anyone need 16 envars? Do you have 16 repositoryies? Or do you
> propose the substitution to be for the whole URL, not just the repository
> root?

No, I don't suggest or propose it, i simply pointed it out because
Julian suggested they might use the shell and substitute more than just
the entire repository root (which is what would require so many env
vars).

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 3 14:44:22 2005

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.