Reported by Unknown User, Oct 8, 2003
(This entry was imported from the savannah tracker, original location: https://savannah.nongnu.org/bugs/index.php?5814) Attic files need to have special treatment for their lifecycle in manifests.
Comment 1 by Unknown User, Apr 14, 2004
Note that with a modern cvs, an Attic file has no special meaning. Or, rather, it does mean that the tip of the trunk is dead -- but that information is also encoded in the state field, which must be handled properly anyhow. Occasionally you may run across a repository which has both "foo,v" and "Attic/foo,v". For instance, in classpath there is javax/swing/plaf/UIResource.java,v which is duplicated in Attic/. In the classpath case this seems to be a bogus repository. In this case the information in the files in Attic could meaningfully be merged into the information from the "real" ,v file -- or it could be ignored as well. I've heard on irc that netbsd does this as well, using a hacked cvs. I don't know what the semantics of this are. I suggest that if monotone sees both such files it just give an error for the time being.
Comment 2 by Thomas Keller, Oct 10, 2010
Summary: handle attic files properly on CVS import