Re: I, too, miss tags.

On Monday 27 February 2006 17:45, you wrote:

> Ok so now my repository looks like this:
>
> /
>         /trunk
>         /branches
>                 /project1
>                 /project2
>                 /project3
>
> And I have a property at / saying r100:VERSION_1_0
>
> Revision 100 of what? Which one of the 4 copies of my application @ r100
> represents VERSION_1_0?

As you have assigned it, VERSION_1_0 pertains to all you three projects. Quite
a plausible scenario if your projects are so closely related that they were
tested, validated and released simultaneously (say, a server and a client
with an evolving protocol).

If this is not what you mean, you could assign label 'r100:PROJ1_VERSION_1_0'
at /, or 'r100:VERSION_1_0' at /branches/project1

> That was my point when I said ... "Unless you have a trunkless/branchless
> repository, simply creating a textual alias for a revision number is
> useless".

To me, your above example proves that it is not useless.

> If the cheap label solution in SVN is going to work at all, it
> has to at least include a URL you tag.

The URL in the tag is the thing that I need least at the moment.

> That way at least it's a label-like
> implementation of the cheap copy mechanism.

We are *not* going to reimplement "the cheap copy mechanism". It is present
already in Subversion, and I (we, label proponents if you want) do not find
it convenient.

There is a need for symbolic names for *revisions*.

-- 
Dr. Saulius Gražulis
Institute of Biotechnology
Graiciuno 8
LT-02241 Vilnius
Lietuva (Lithuania)
fax:          (+370-5)-2602116
tel.: office: (+370-5)-2602556
      mobile: (+370-684)-49802, (+370-614)-36366
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org