1 |
james |
2 |
# Three different line formats are valid: |
2 |
|
|
# key -a aliases... |
3 |
|
|
# key [options] directory |
4 |
|
|
# key [options] directory files... |
5 |
|
|
# |
6 |
|
|
# Where "options" are composed of: |
7 |
|
|
# -i prog Run "prog" on "cvs commit" from top-level of module. |
8 |
|
|
# -o prog Run "prog" on "cvs checkout" of module. |
9 |
|
|
# -e prog Run "prog" on "cvs export" of module. |
10 |
|
|
# -t prog Run "prog" on "cvs rtag" of module. |
11 |
|
|
# -u prog Run "prog" on "cvs update" of module. |
12 |
|
|
# -d dir Place module in directory "dir" instead of module name. |
13 |
|
|
# -l Top-level directory only -- do not recurse. |
14 |
|
|
# |
15 |
|
|
# NOTE: If you change any of the "Run" options above, you'll have to |
16 |
|
|
# release and re-checkout any working directories of these modules. |
17 |
|
|
# |
18 |
|
|
# And "directory" is a path to a directory relative to $CVSROOT. |
19 |
|
|
# |
20 |
|
|
# The "-a" option specifies an alias. An alias is interpreted as if |
21 |
|
|
# everything on the right of the "-a" had been typed on the command line. |
22 |
|
|
# |
23 |
|
|
# You can encode a module within a module by using the special '&' |
24 |
|
|
# character to interpose another module into the current module. This |
25 |
|
|
# can be useful for creating a module that consists of many directories |
26 |
|
|
# spread out over the entire source repository. |