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

RE: I miss tags

From: Sean Johnston <sean.johnston_at_xenicom.com>
Date: 2004-09-28 11:59:01 CEST

From: Tom McMillen [mailto:thomas.mcmillen@mppglobal.com]
Sent: 28 September 2004 09:49

> if you changed
> svn cp
> to
> svn tag
> would this make the mental mapping easier.... You are now no longer
> but you are now tagging.... (at least in your mind, to svn it is still a
> copy)

Personally to me I have no problem with using the copy functionality for
tagging bits of the repository. It is a slightly different nomenclature but
I can easily see that it is offering the same functionality. Or is it ... ?

The answer to that is NO.

It only offers the same functionality if I have implemented an additional
pre-commit hook that prevents people from committing changes to that copy.

This pre-commit hook will also look at user entered text (i.e. the name of
the copied directory) to identify stuff that should not be committable. So,
what happens if I typo the name of my tag (e.g. /repos/tagss/mytagwhatever).
Now I have created a copy that isn't equivalent to a tag because my
pre-commit hook is only looking for /repos/tags/*.

Doing anything on user entered text is always going to be prone to error.
That is why you code systems up to perform common operations and implement
common restrictions.

File systems, for example, aren't set up so that to make a read-only file
you put it in a specific directory.

Someone mentioned locking up and coming for future releases. Hopefully this
will provide a way to make a copy and then lock it down against any changes.


This message has been checked for all known viruses by Xenicom delivered through the MessageLabs Virus Control Centre.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Sep 28 12:00:23 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.