>
> > if you changed
> > svn cp
> > to
> > svn tag
> >
> > would this make the mental mapping easier.... You are now no longer
> copying,
> > 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/*.
>
so what if...
svn tag repos/trunk/myproject mytagwhatever
if svn tag could go to a pre-commit hook that could manage the tags directory and
ensure that mytagwhatever tag goes to /repos/tags our poor typing skills would be less of a problem?
> 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.
>
Agreed, but could this extended functionality possibly not need to be part of the core svn system?
(I think I'm looking for a third way where people who want tags can have them and those that don't,
don't install the additions....)
---------------------------------------------------------------------
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:39:47 2004