Although I love CVS (most of the time:)  I've always been annoyed with
the fact that branches and tags are handled by the same command (cvs tag and
cvs rtag).  However it makes sense to be able to refer to both in the same
manner for 'cvs update', with the -j and -r parameters in those contexts.
Having 'cvs tag -b' and 'cvs tag' to differentiate between checkpoint vs
branch requires explaining a lot of extra stuff to the newbies, and is
mostly a throwback to the programming logic going on behind the scenes.  I'm
sure it makes sense as a CVS maintainer/programmer to have -b be an option
to tag, but on the user end it should probably be a different (but similar)
command

cvs 'branch' | cvs 'rbranch' :  same as cvs tag but assumes -b, and does not
understand -F.  I assume taginfo logic would need to be virtually duplicated
and some file like 'branchinfo' be created to handle these operations.

cvs 'tag' | cvs 'rtag' : same as existing cvs tag but -b no longer is an
option, and -F only works on tags

    Behind the scenes the uniqueness in tag names would still be required,
but it should never be possible to convert the meaning one to the other.
Note this is quite different from going back to an existing marker tag and
creating a branch from it with some other name (which is a common
occurence).  In addition, both commands should probably be able to rename a
tag, a feature that as far as I can tell, does not exist in CVS at all.

    - Sean

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 29, 2000 10:06 AM
Subject: Disable "cvs tag -F" of branch tags


> Greetings!
>
> Our developers will tag their code for builds under test, and when
problems
> are fixed, they will move the current tag until the product is shipped and
> the tag is frozen.  Occasionally, someone makes the mistake of moving the
> branch tag instead of one of the branch's static tags.  The problem here
is
> that the tag is converted into a static tag.  Sometimes it's hard to
recover.
>
> Maybe this falls under the "yeah, and any idiot who accidently types
'rm -rf
> /usr' should have to accept the price", but it would sure seem like an
easy
> fix for CVS to not allow the -F option when the tag is a branch tag.
>
> What do YOU guys think?
>
> :)hal mahaffey
>
>

Reply via email to