Re: Tag locking change

[Paul Sander]

>--- Forwarded mail from address@hidden

>[ On Tuesday, October 8, 2002 at 16:11:42 (-0700), Paul Sander wrote: ]
>> Subject: Re: Tag locking change
>>
>> >--- Forwarded mail from address@hidden
>> 
>> >Mark writes:
>> >> 
>> >> If one wants to tag the latest on a branch, why should one have to create 
>> >> a
>> >> workarea to do it?
>> 
>> >How do you know you want to tag the latest on a branch?  Either you have
>> >no idea what the "latest" actually is, or you know that no one is going
>> >to be trying to commit changes while you're tagging the files.  In
>> >neither case is directory-at-a-time locking going to make any difference.
>> 
>> Most of the time it's the former.  But you do know what was "latest at
>> a given time".  And "a given time" could possibly be "now".


>Ah, no, you don't _know_ that for the time "now" because if you did then
>you would have a working directory which contains that state and
>therefore no need to use 'cvs rtag'.

Who do you mean by "you" here?  *I* might have an up to date working
directory, but the guy creating the tag may not.  It's also not too hard
to tell everybody to hold their breath for a minute while the command is
typed, provided there's enough discipline to *know* that the latest
committed versions are the proper ones for the tag.  (Note that there's
a distinction between "knowing" and *knowing* here.  That distinction is
that "knowing" is hoping that something is true, *knowing* is being
absolutely certain that something is true.)

>(and for any time but "now" you can give 'cvs rtag' an explicit '-D')

Actually, I think "-Dnow" works.  It'd be nice if it could be given in
conjunction with a branch tag in this context.  Then it could be made
the default, or put in the user's .cvsrc file.

>--- End of forwarded message from address@hidden