[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: Karl Heinz Marbaise <khmarbaise_at_gmx.de>
Date: Fri, 08 Oct 2010 14:35:19 +0200

Hi Tino,

>> 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?

It was just an example how it might look like....

>
> I always wanted something like "repository path of current working copy"
> - is that what you mean?
No...the repository path can be seen if you do an svn info in your wc.

> 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 ;).

Lets assume the following repository structure...to make my explanation
more clear (Or may be i misunderstand yours?)...

/
+---- px
        +--- py
              +--- pz
                    +--- trunk
                    +--- tags
                    +--- branches

If you do a checkout from the above trunk you need to do the following
to create a tag (svn 1.5, 1.6):

     svn cp ^/px/py/pz/trunk ^/px/py/pz/tags/R1 -m"- Tag"

So what a like to see is something like:

     svn cp ^!/trunk ^!/tags/R1 -m"- Tag"

cause i have often repositories with a deep folder structures in it.

So this would be very convenient.

Kind regards
Karl Heinz Marbaise

-- 
SoftwareEntwicklung Beratung Schulung    Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise        ICQ#: 135949029
Hauptstrasse 177                         USt.IdNr: DE191347579
52146 Würselen                           http://www.soebes.de
Received on 2010-10-08 14:36:01 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.