Re: I, too, miss tags.

On Sunday 26 February 2006 19:33, Scott Palmer wrote:

> > Since all labels would be stored in one property, a label per line,  
> > listing
> > and searching would be fast and efficient.

> This is what I was going to suggest, EXCEPT I think the property  
> should go on the branch you are labeling.  So it would be a property  
> of the top directory in your WC.

I think a tool can and should accommodate both ways. There can be a list of
labels attached to any object in the repo that takes properties, for that
matter...

The only problem might be that there will be extra complication to find all
such list of labels. One would not want to traverse the whole directory tree
when a label is requested.

I think the label lists can be searched at least in three places:

1) CWD
2) Root of the WC
3) Root of the repo

Whatever is found first, wins.

Label lists would always be taken from HEAD revision, so that we can go
forward in time, not only back.

What about such policy?

> That way there is still the  
> separation of unrelated labels and the same label name can be used in  
> different projects in the same repo.. e.g.  "last_merge" can be in  
> ProjectA/trunk and ProjectB/trunk and each will point to a different  
> revision.

Exactly.

This shows how labels can easily accommodate multiple project per repo, if one
wishes so. :)

> The repo root could also be used for repo-wide labels.

Absolutely. For small projects, like most of mine are, this would be more than
enough. For large ones, one could attach label lists to the root of each
project.

I find this a nice scheme.

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