[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tag locking change

From: Greg A. Woods
Subject: Re: Tag locking change
Date: Wed, 9 Oct 2002 02:15:58 -0400 (EDT)

[ On Tuesday, October 8, 2002 at 22:32:18 (-0700), Mike Ayers wrote: ]
> Subject: Re: Tag locking change
> Greg A. Woods wrote:
> > If you really Really REALLY want to tag the head of a branch then just
> > check out the branch (or do a "cvs update" in any existing working
> > directory which has no un-committed changes) then then apply the tag to
> > what you get as a result by running "cvs tag" in that working directory.
> > That way you can know ahead of time exactly what you've got.  It's then
> > up to the user whether or not they actually look to see what's there
> > before they tag it.
>       What I fail to understand is why anyone would want to tag the head of 
> a branch in an instantaneous fashion.

Me too!  :-)

>  Wouldn't you want to 
> build/test, etc. first?

Well, in theory you could check out a working directory with the new tag
and test it then, and you could adjust the tagged revision in any files
where some unexpected change had in fact crept in.

It does seem like the wrong way to go about things though especially
when you can just update a working directory and then be certain that
what you tag is correct in the first place.

>       I'm kind of lost on what the point of contention is here.  What is it 
> that someone would want to do that is affected by the tag locking 
> change?  Could someone please clarify?

I think the issue is some of us don't want 'cvs rtag' to "work" when the
intent is to tag the head of a branch, especially not with the new more
per-directory-only locking scheme it will use to work faster and to
cause less contention (i.e. it should give a usage error).  Other people
seem to think that indeed it should be possible to tag the head of a
branch with 'cvs rtag'.

Indeed silly tricks could still be done with the likes of specifying a
time only one second prior to the current time.  Of course the very idea
of using timestamps is open to question as well since unless you have
some external way to ensure the repository is quiescent for a decent
window of time you still can't know what you're tagging.

CVS just gives users far too much rope for many tasks.

                                                                Greg A. Woods

+1 416 218-0098;            <address@hidden>;           <address@hidden>
Planix, Inc. <address@hidden>; VE3TCP; Secrets of the Weird <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]