[cvsnt] builds 68 & 72: more errors resurrecting files from attic

[Gary Newman]

Hi Tony,

If someone erroneously removes a file, admin seems the right way to recover it.  Using
admin all the previous history is preserved whereas adding the file back in loses all
that, doesn't it?  Does adding it back in with the same name keep the log entry for the
removal and log it getting added back as well?  That makes sense for a file that is
removed in one release and then at a later date reinstituted...  Let me know, eh?

    -Gary-

Tony Hoyle wrote:

> On Tue, 04 Mar 2003 18:58:10 -0500, Gary Newman
> <REMOVE_THIS_NOSPAMgnewman at belarc.com> wrote:
>
> >I'm still having a very similar problem with the attic on builds 68 & 72 on a Windows
> >2000 server but with no error message.
> >
> >I remove a file (say its at revision 1.1) and commit it and it goes into the Attic
> >just fine (as r1.2).  Then I obsolete the new revision (cvs admin -o 1.2 filename)
> >and that works fine, but the file stays in the Attic.
> >
> >To see what's going wrong, I saved the r1.1 file outside the attic before I started
> >this test, and diffed with the Attic version after obsoleting r1.2 and they are
> >identical.  So it seems that the bug is solely in cvsnt not moving the file out of
> >the attic when the version that put it in the attic as 'dead' is obsoleted.
> >
> The correct way to undelete a file is to 'cvs add' it again, not to try to run
> cvs admin on it.  'cvs admin' bypasses the whole of CVS and operates on the
> RCS file directly, and should not be used unless you have very specific
> requirements and know what the consequences will be.
>
> TBH I'd rather remove the whole command but it has its uses sometimes.
>
> Tony