1 (This README file is not an RCS ,v file, so cvs2svn won't notice it.)
3 This directory, the `proj' project, is for testing cvs2svn's ability
4 to group revisions correctly along tags and branches. Here is its
7 1. The initial import (revision 1.1 of everybody) created a
8 directory structure with a file named `default' in each dir:
19 2. Then tagged everyone with T_ALL_INITIAL_FILES.
21 3. Then tagged everyone except sub1/subsubB/default with
22 T_ALL_INITIAL_FILES_BUT_ONE.
24 4. Then created branch B_FROM_INITIALS on everyone.
26 5. Then created branch B_FROM_INITIALS_BUT_ONE on everyone except
27 /sub1/subsubB/default.
29 6. Then committed modifications to two files: sub3/default, and
32 7. Then committed a modification to all 7 files.
34 8. Then backdated sub3/default to revision 1.2, and
35 sub2/subsubA/default to revision 1.1, and tagged with T_MIXED.
37 9. Same as 8, but tagged with -b to create branch B_MIXED.
39 10. Switched the working copy to B_MIXED, and added
40 sub2/branch_B_MIXED_only. (That's why the RCS file is in
41 sub2/Attic/ -- it never existed on trunk.)
43 11. In one commit, modified default, sub1/default, and
44 sub2/subsubA/default, on branch B_MIXED.
46 12. Did "cvs up -A" on sub2/default, then in one commit, made a
47 change to sub2/default and sub2/branch_B_MIXED_only. So this
48 commit should be spread between the branch and the trunk.
50 13. Do "cvs up -A" to get everyone back to trunk, then make a new
51 branch B_SPLIT on everyone except sub1/subsubB/default,v.
53 14. Switch to branch B_SPLIT (see sub1/subsubB/default disappear)
54 and commit a change that affects everyone except sub3/default.
56 15. An hour or so later, "cvs up -A" to get sub1/subsubB/default
57 back, then commit a change on that file, on trunk. (It's
58 important that this change happened after the previous commits
61 16. Branch sub1/subsubB/default to B_SPLIT, then "cvs up -r B_SPLIT"
62 to switch the whole working copy to the branch.
64 17. Commit a change on B_SPLIT, to sub1/subsubB/default and