> -----Original Message-----
> From: David Weintraub [mailto:qazwart_at_gmail.com]
> Sent: Tuesday, May 19, 2009 4:19 PM
> To: Bolstridge, Andrew
> Cc: users_at_subversion.tigris.org
> Subject: Re: Subversion misses (was RE: Subversion vs. StarTeam)
>
> On Tue, May 19, 2009 at 4:46 AM, Bolstridge, Andrew
> <andy.bolstridge_at_intergraph.com> wrote:
>
> >> Misses:
> >> * Really needs the ability to tag even if tag is just an alias to
> >> revision number.
> >
> > This made me think (at the risk of reopening old wounds) wouldn't it
> be really,
> > really easy to keep a file on the server that stored a list of text
> 'tags' and a
> > corresponding revision number? Then you can very easily 'tag' the
> repository
> > (thanks to the excellent concept that the revision number refers to a
> unique point-
> > in-time) and retrieve a fixed snapshot using a descriptive term
> instead of having
> > to remember the revnum.
>
> We did a similar work around with SCCS which also didn't have the
> concept of a tag or label. In SCCS, you created a "tag" by creating a
> file with a list of all the files and revisions that were included in
> that tag, a shell script to be written to checkout that tag if you
> needed it.
>
>
> It's just that's it's a bit clumsy, and every time we do this, it
> reminds us that Subversion doesn't have true tagging. Oh, even if a
> tag is just a revision number alias, you could do things like this:
>
> $ svn diff -rREL-1.0:REL-1.1 http://subversion/dev/proj/trunk
>
> It's just seems like something that should have been engineered into
> Subversion from the very beginning. It's like someone wrote down a
> list of requirements for a revision control system, and the list was
> too long to fit on one page, so tagging was placed on the back, and
> the programmer didn't see it.
I was browsing the dev list today, and I found a message from someone who suggested just this - store a label to revnum mapping in revprop 0. Unfortunately he didn't get too favourable a response, possibly because the flamewar of "branching v labelling" was still too fresh.
I still think it's a great idea, but I feel the devs think that the branch facilities are so great that they *should* be used for tagging. The main argument seemed to be a lack of auditing - set the label, you have no means of determining who did it, when or if anyone changed it. (so perhaps it gets stored as a revprop in the project you're labelling, but with the corresponding 'index' written to revprop 0).
I don't like the tag functionality so far - I'd have created thousands of branches to date if we used it (as we release every little change explicitly for our customers)
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2315173
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-19 18:35:22 CEST