[ On Wednesday, March 29, 2000 at 17:07:54 (-0600), David Thornley wrote: ]
> Subject: Re: Disable "cvs tag -F" of branch tags
>
> Yup. About fifteen minutes ago, I typed the wrong tag and changed
> a branch tag into a normal tag. This would not have happened if
> the restriction above had been in place.
Sorry to hear that....
> I have mistyped things in the past. I have every reason to believe I
> will mistype things in the future. I appreciate all the help I can
> get to make sure these mistypings don't do anything too bad.
I too have done this more than I care to admit.....
> In this case, it looks irrecoverable. I updated to the correct
> revision and created a new branch tag with the old branch tag name,
> but this will mean that any future revisions on that branch will
> have a six-digit revision number rather than a four. I've effectively
> cut off a branch and added a twig. If I'm lucky, nobody's going to
> change that branch any more.
If you can find a working directory on that branch that is reasonably
up-to-date, but unchanged since the branch tag was deleted then you can
recover the branch tag 100%. It's just very tedious to do as you have
to re-add the tag on a file-by-file basis after examining the "ancestor"
revision of every file and decoding the branch revision-ID if there has
been a commit to the file, or simply creating the branch from the
ancestor revision if there hasn't been any commit. I've always used
"cvs admin" to re-create the tags, though I don't know if that's
necessary. I suppose it could be automated but I don't know of anyone
who has written such a script to date. I've never had to do such a fix
in a module of more than a dozen or so files, fortunately.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <robohack!woods>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
