Call me paranoid, but I'd probably just 'cvs add' the file again.
As for changing an RCS file killing you, Michael, I'm pretty sure that the rumor
about the CVS RCS code occassionally changing the sync rate of video cards and
causing monitors to explode really is just a rumor, but you never know.
I suppose I've had bosses that made me think twice about making mistakes, as well,
but I don't like to work for them for long. ;)
Derek
--
Derek Price CVS Solutions Architect
mailto:[EMAIL PROTECTED] OpenAvenue ( http://www.OpenAvenue.com )
--
"Those who make peaceful revolution impossible will make violent revolution
inevitable."
-- John F. Kennedy
Noel L Yap wrote:
[snip]
> The way I'd attack this problem would be to:
> 1. add a new file
> 2. copy the archive
> 3. remove the file
> 4. diff the archive against the previous one
[snip]
> [EMAIL PROTECTED] on 05/21/2000 11:08:22 PM
>
> To: [EMAIL PROTECTED]
> cc: (bcc: Noel L Yap)
> Subject: Re: Bug (?) in branching support / removed files
>
> I am looking for help from someone who knows the RCS file
> format quite well. Noel, this probably means you :-)
>
> About a week ago, I had a problem.
> In summary, I made changes to a working directory, including
> deleting files; I then tried to commit to a branch.
> Unfortunately, the deleted files were deleted from the
> trunk, not from the branch.
[snip]
> I don't know the ins and outs of RCS file formats. My
> current thought/plan is to edit all the files in the attic,
> change the RCS line that identifies the 'dead' state, and
> then put them back into the non-attic storage section.
>
> Is this kosher? Will this work? Are there any pitfalls that
> I don't know of that will kill me?
>
> Michael