Re: [DESIGN] Aliases? (Was: RE: Re: I, too, miss tags.)

On Friday 24 February 2006 17:52, Vincent Starre wrote:

> Such would need to be client-side in order to make any sense at all, and
> that itself doesnt make any sense at all :)
> ...

I am afraid I can not follow you here. Why it does not make sence?

A list of revision labels would be a per-repository (non-versioned) property;
when client sets a label, it will be committed and stored in the repo. When
other clients update, they will get a new list of labels each time. Conflicts
would be handled as usual. Seems clean.

The only extra thing that comes to me is that you probably do not want some
labels to be arbitrarily removed (say, you do not want to VER-2.0 label to
disappear misteriously ;). Thus, some labels should be marked as
"non-mutable", and/or only an original committer should be able to change the
label (which would imply that the committers name would be changed along with
the labels and revision).

Regards,
Saulius.

-- 
Saulius Gražulis
Visuomeninė organizacija "Atviras Kodas Lietuvai"
P.Vileišio g. 18
LT-10306 Vilnius
Lietuva (Lithuania)
tel/fax:      (+370-5)-210 40 05
mobilus:      (+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