In the following situation 'cvs co' and 'cvs up'
understood when to include a file or not depending on
the working branch tag. However internally it stores
the file in the Attic when it isn't in the MAIN branch.
This causes cvsweb to place the file in the Attic even
if the branch it is in is selected or not.
For Example:
PROMPT$ cvs co MyModule
cvs checkout: Updating MyModule
U MyModule/foo1
PROMPT$ cd MyModule
PROMPT$ cvs tag -b dev-branch
cvs tag: Tagging .
T foo1
PROMPT$ cvs up -r dev-branch
cvs update: Updating .
PROMPT$ echo "Hello World" > bar2
PROMPT$ cvs add bar2
cvs add: scheduling file `bar2' for addition on branch
`dev-branch'
cvs add: use 'cvs commit' to add this file permanently
PROMPT$ cvs ci -m "added bar2 to branch dev-branch"
cvs commit: Examining .
RCS file: /cvsroot/MyModule/bar2,v
done
Checking in bar2;
/cvsroot/MyModule/bar2,v <-- bar2
new revision: 1.1.2.1; previous revision: 1.1
done