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

Re: [RFC] caret notation enhancement

From: Tino Schwarze <subversion.lists_at_tisc.de>
Date: Fri, 8 Oct 2010 12:01:09 +0200

Hi Karl Heinz,

On Fri, Oct 08, 2010 at 11:25:56AM +0200, Karl Heinz Marbaise wrote:

> i've a suggestion about the caret notation which is very handy in daily
> work.
>
> The caret syntax is very helpfull if you're working with a repository
> which contains only a single project and of course makes life easier.
>
> svn cp ^/trunk ^/tags/RELEASE-1.0.0 -m"- Tagging"
>
>
> But unfortunately i don't have often the pleasure to work with such
> repositories. The usual case is to have multiple projects inside a
> repository. The result of this is the following:
>
> svn cp ^/path/trunk ^/path/tags/RELEASE-1.0.0 -m"- Tagging"
>
> The part "path" becomes longer and longer the more projects are
> contained in such a repository or depending of the structure of the
> projects/modules.
>
>
> So i would like to suggest to introduce an enhancement of the
> caret syntax to get to a shorter way of writing the things for
> tagging/branching.
>
> svn cp ^^/trunk ^^/tags/RELEASE-1.0.0 -m"- Tagging"
>
> The usage of the doubled ^ is just as an example, cause i know
> on Windows you already have to type the doubled ^ because of the shell.

So what should ^^ (or however it turns out) mean, exactly?

I always wanted something like "repository path of current working copy"
- is that what you mean? Maybe ^: could be used as the anchor for
"repository path of current working copy", if you are in a copy of
/some/path/to/project/branch/whatever you might use

  svn cp ^: ^:../../tags/newtag

to copy that path to /some/path/to/project/tags/newtag.

Might be difficult to implement, I suppose but IANAD ;).

Tino.

-- 
"What we nourish flourishes." - "Was wir nähren erblüht."
www.tisc.de
Received on 2010-10-08 12:01:48 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.