[EMAIL PROTECTED] wrote:

> 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?
        [smc]  Some time ago, I had made an 
        (admittedly idle) proposal to add a
        command which might export a tag 
        file that would contain a definition of
        all the tags and what revisions of what 
        files they referred to.

        That way, you could do something like this:

        1.  restore your pre-disaster repository from backups
             to some new disk space someplace
        2.  cvs export_tag lost_tag > lost_tag_file
        3.  go to your real repository
        4.  cvs import_tag < lost_tag_file

        Or something along those lines.

        Of course nothing became of my idle prattlings, 
        as is normally the case when it comes to CVS.

Reply via email to