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

Re: Mnemonic names for revisions?

From: S.Ramaswamy <ramaswamy_at_collab.net>
Date: 2004-09-09 09:07:21 CEST

Wolfgang Fritz wrote:

>Hello,
>
>I'm in the process of switching from CVS to subversion because of the
>well known advantages of subversion over CVS.
>
>One of the major differences between CVS and subversion is the handling
>of tags. In CVS, tags are needed to "mark" a certain state of the
>repository in order to be able to get that state back later. In
>subversion, you get this for free because each revision _is_ a certain
>state of the repository.
>
>But you have to remember the revision number. So my question:
>
>Is there a way to give a certain revision a mnemonic name?
>
>I know the suggestion from the book to create a tags subdirectory and
>copy "tagged" revisions to it, but I must say I don't like this approach
>too much. It's kind of overkill for the simple problem of remembering a
>certain revision by a mnemonic name, and it can be plain dangerous if
>you don't disable "commit-like" modifications to the tags directory.
>
>
Why is it a overkill ? With 'cvs tag' the time it takes depends on the
size of the directory that is being tagged; svn tagging is a constant
time operation. If permissions on tag-directories is your concern, you
might want to check out the section on setting per-directory
permissions in chapter 6 of the svn book

Ramaswamy

>Wolfgang
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 9 09:09:13 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.