Next: [[cvs: The CVS directory in the repository#The CVS directory in the repository|CVS in repository]], Previous: [[cvs: File Permission issues specific to Windows#File Permission issues specific to Windows|Windows permissions]], Up: [[cvs: How data is stored in the repository#How data is stored in the repository|Repository storage]] |[[cvs: Index#SEC_Contents|Contents]]||[[cvs: Index#Index|Index]]|

----

==== The attic ====

You will notice that sometimes CVS stores an RCS file in the `Attic`. For example, if the CVSROOT is ‘`/usr/local/cvsroot`’ and we are talking about the file ‘`backend.c`’ in the directory ‘`yoyodyne/tc`’, then the file normally would be in

/usr/local/cvsroot/yoyodyne/tc/backend.c,v

but if it goes in the attic, it would be in

/usr/local/cvsroot/yoyodyne/tc/Attic/backend.c,v
instead. It should not matter from a user point of view whether a file is in the attic; CVS keeps track of this and looks in the attic when it needs to. But in case you want to know, the rule is that the RCS file is stored in the attic if and only if the head revision on the trunk has state `dead`. A `dead` state means that file has been removed, or never added, for that revision. For example, if you add a file on a branch, it will have a trunk revision in `dead` state, and a branch revision in a non-`dead` state.

This document was generated on a sunny day using [http://www.nongnu.org/texi2html/ texi2html].