📄 1118-1118.html
字号:
<HTML>
<HEAD>
<TITLE>Linux Complete Command Reference:File Formats:EarthWeb Inc.-</TITLE>
</HEAD>
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
<SCRIPT>
<!--
function displayWindow(url, width, height) {
var Win = window.open(url,"displayWindow",'width=' + width +
',height=' + height + ',resizable=1,scrollbars=yes');
}
//-->
</SCRIPT>
</HEAD>
-->
<!-- ISBN=0672311046 //-->
<!-- TITLE=Linux Complete Command Reference//-->
<!-- AUTHOR=Red Hat//-->
<!-- PUBLISHER=Macmillan Computer Publishing//-->
<!-- IMPRINT=Sams//-->
<!-- CHAPTER=05 //-->
<!-- PAGES=1103-1208 //-->
<!-- UNASSIGNED1 //-->
<!-- UNASSIGNED2 //-->
<P><CENTER>
<a href="1116-1117.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="1119-1120.html">Next</A></CENTER></P>
<A NAME="PAGENUM-1118"><P>Page 1118</P></A>
<TABLE>
<TR><TD>
</TD><TD>
contain either other module names or paths. When you use paths in aliases,cvs <BR>
checkout creates all intermediate directories in the working directory, just as if the <BR>
path had been specified explicitly in the cvs arguments.
</TD></TR><TR><TD>
</TD><TD>
mname [ options ] dir [ files ... ] [&module ...]
</TD></TR><TR><TD>
</TD><TD>
In the simplest case, this form of module definition reduces to mname dir. This <BR>
defines all the files in directory dir as module mname. dir is a relative path (from<BR>
$CVSROOT) to a directory of source in one of the source repositories. In this case, <BR>
on checkout, a single directory called mname is created as a working directory; no <BR>
intermediate directory levels are used by default, even if dir was a path involving <BR>
several directory levels. By explicitly specifying files in the module definition after <BR>
dir, you can select particular files from directory dir. The sample definition for <BR>
modules is an example of a module defined with a single file from a particular <BR>
directory. Here is another example:
</TD></TR><TR><TD>
</TD><TD>
m4test unsupported/gnu/m4 foreach.m4 forloop.m4
</TD></TR><TR><TD>
</TD><TD>
With this definition, executing cvs checkout m4test will create a single working <BR>
directory m4test containing the two files listed, which both come from a<BR>
common directory several levels deep in the cvs source repository. A module <BR>
definition can refer to other modules by including &module in its definition. The <BR>
checkout command creates a subdirectory for each such module in your working <BR>
directory. New in cvs 1.3; avoid this feature if sharing module definitions with <BR>
older versions of cvs.
</TD></TR><TR><TD>
</TD><TD>
Finally, you can use one or more of the following options in module definitions: <BR>
_d name names the working directory something other than the module name. <BR>
This option is new in cvs 1.3; avoid this feature if sharing module definitions <BR>
with older versions of cvs. _i prog allows you to specify a program prog to run <BR>
whenever files in a module are committed. prog runs with a single argument, the <BR>
full pathname of the affected directory in a source repository. The commitinfo, <BR>
loginfo, and editinfo files provide other ways to call a program on commit. _o <BR>
prog allows you to specify a program prog to run whenever files in a module are <BR>
checked out. prog runs with a single argument, the module name. _e prog allows <BR>
you to specify a program prog to run whenever files in a module are exported. <BR>
prog runs with a single argument, the module name. _t prog allows you to <BR>
specify a program prog to run whenever files in a module are tagged. prog <BR>
runs with two arguments: the module name and the symbolic tag specified to rtag. _u <BR>
prog allows you to specify a program prog to run whenever cvs update is executed <BR>
from the top-level directory of the checked-out module. prog runs with a single <BR>
argument, the full path to the source repository for this module.<BR>
</TD></TR><TR><TD>
commitinfo, loginfo, rcsinfo, editinfo
</TD><TD>
These files all specify programs to call at different points in the cvs commit <BR>
process. They have a common structure. Each line is a pair of fields: a regular <BR>
expression, separated by whitespace from a filename or command-line template. <BR>
Whenever one of the regular expression matches a directory name in the<BR>
repository, the rest of the line is used. If the line begins with a # character, the <BR>
entire line is considered a comment and is ignored. Whitespace between the <BR>
fields is also ignored. For loginfo, the rest of the line is a command-line template <BR>
to execute. The templates can include not only a program name, but also <BR>
whatever list of arguments you want. If you write %s somewhere on the argument <BR>
list, cvs supplies, at that point, the list of files affected by the commit. The first <BR>
entry in the list is the relative path within the source repository where the change <BR>
is being made. The remaining arguments list the files that are being modified, <BR>
added, or removed by this commit invocation. For taginfo, the rest of the line is <BR>
a command-line template to execute. The arguments passed to the command are,
</TD></TR></TABLE>
<P><CENTER>
<a href="1116-1117.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="1119-1120.html">Next</A></CENTER></P>
</td>
</tr>
</table>
<!-- begin footer information -->
</body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -