[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Tags

From: Marcus Rueckert <darix_at_web.de>
Date: 2006-07-01 05:14:49 CEST

On 2006-07-01 01:22:13 +0200, hakon@ion.no wrote:
> 1. The user should not need to be bothered with _where_ the tag will be
> stored.

how about large scale multi project repositories like apache?
how should your concept work there?

i expect an "you will have a config for that" ... now ... that means you
would need to add some sort of "project" to the svn concepts so you can
configure a project and define which will be the location for tags of
this project.

> 2. The Subversion 'tag concept'* should be the same as other VCS', as the
> Subversion concept does not add any value and confuses newcomers.

do the other SCM handle tags from working copies as well? like tagging
a mixed revision working copy (to preserve its state)

> 4. Subversion should 'know' of tags. E.g. look at what Subclipse have done
> because Subclipse knew about the tags, and realise that Subversion should
> support this natively. (Now the user had to locate the tags directory for
> Subclipse.) In an earlier email I was telling about a possible 'svn
> taglist' command that displays "TAG REVISION AUTHOR DATE" for all tags,
> which is excactly the command-line version of one of the features of
> Subclipse.
> 5. Subversion should get a 'tag' command to make the intention clear. (In
> its simplest form, it could be another alias for 'copy'.)
> 6. Subversion should provide a more compact syntax for tagging. Say 'svn
> tag -r REVISION TAG', or 'svn tag --force NEWREVISION' to update an
> already set tag, or 'svn taglist' for displaying tags.

how should this single revision for a tag concept handle tags from
working copies? how does subclipse handle that case?

and if you like to argue that use case is rare .... every svn release is
done that way. and i wouldnt wonder if the same is true for apache/apr

for more see: http://svn.collab.net/repos/svn/trunk/notes/releases.txt

> *) The Subversion concept of a tag is that it is a directory (in HEAD).
> While other VCS uses a concept of tags which is a revision number (or a
> path and a revision number).
> The proposed solution of putting tags as special properties solves all of
> them.

no, it does not.
while your tagging mechanism seems to be simpler at first
look, it doesnt have the full power of svn tags.


           openSUSE - SUSE Linux is my linux
               openSUSE is good for you
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 1 05:15:17 2006

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.