📄 0095-0096.html
字号:
<HTML>
<HEAD>
<TITLE>Linux Complete Command Reference:User Commands: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=01 //-->
<!-- PAGES=0001-0736 //-->
<!-- UNASSIGNED1 //-->
<!-- UNASSIGNED2 //-->
<P><CENTER>
<a href="0093-0094.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="0097-0097.html">Next</A></CENTER></P>
<A NAME="PAGENUM-95"><P>Page 95</P></A>
<TABLE>
<TR><TD>
_l
</TD><TD>
Local; run only in current working directory, rather than recurring through subdirectories.
Available with the following commands: checkout,
commit, diff, export, remove, rdiff, rtag, status,
tag, and update.
</TD></TR>
</TABLE>
<CENTER>
<TABLE BGCOLOR="#FFFF99">
<TR><TD><B>
WARNING
</B></TD></TR>
<TR><TD>
<BLOCKQUOTE>
This is not the same as the overall cvs _l option, which you can specify to the
left of a cvs command.
</BLOCKQUOTE></TD></TR>
</TABLE></CENTER>
<TABLE>
<TR><TD>
_n
</td><td>
Do not run any
checkout/commit/tag/update program. (A program can be specified to run on each
of these activities, in the modules database; this option bypasses it.) Available with the
checkout, commit, export, and rtag commands.
</TD></TR></TABLE>
<CENTER>
<TABLE BGCOLOR="#FFFF99">
<TR><TD><B>
WARNING
</B></TD></TR>
<TR><TD>
<BLOCKQUOTE>
This is not the same as the overall cvs _n option, which you can specify to the left of a
cvs command.
</BLOCKQUOTE></TD></TR>
</TABLE></CENTER>
<TABLE>
<TR><TD>
_P
</TD><TD>
Prune (remove) directories that are empty after being updated, on checkout, or update. Normally,
an empty directory (one that is void of revision-controlled files) is left alone. Specifying
_P will cause these directories to be silently removed from your checked-out sources. This does not remove the
directory from the repository, only from your checked out copy. Note that this option is implied by the
-r or _D options of checkout and export.
</TD></TR><TR><TD>
_p
</TD><TD>
Pipe the files retrieved from the repository to standard output, rather than writing them in the
current directory. Available with the checkout and
update commands.
</TD></TR><TR><TD>
-r tag
</TD><TD>
Use the revision specified by the
tag argument instead of the default head revision. As well as
arbitrary tags defined with the tag or rtag command, two special tags are always available:
HEAD refers to the most recent version available in the repository, and
BASE refers to the revision you last checked out
into the current working directory. The tag specification is "sticky" when you use this option with
cvs checkout or cvs update to make your own copy of a file:
cvs remembers the tag and continues to use it on future
update commands, until you specify otherwise. tag can be either a symbolic or numeric
tag, in RCS fashion. Specifying the _q global option along with the
-r command option is often useful, to suppress the warning messages when the RCS file does not contain the specified tag.
-r is available with the checkout, commit, diff,
history, export, rdiff, rtag, and update commands.
</table>
<CENTER>
<TABLE BGCOLOR="#FFFF99">
<TR><TD><B>
WARNING
</B></TD></TR>
<TR><TD>
<BLOCKQUOTE>
This is not the same as the overall cvs -r option, which you can specify to the left of a
cvs command.
</BLOCKQUOTE></TD></TR>
</TABLE></CENTER>
<P><B>
cvs COMMANDS
</B></P>
<P>Here (finally) are details on all the cvs
commands and the options each accepts. The summary lines at the top of
each command's description highlight three kinds of things:</P>
<TABLE>
<TR><TD>
Command Options and Arguments
</TD><TD>
Special options are described in detail; common command options may appear
only in the summary line.
</TD></TR><TR><TD>
Working Directory, or Repository?
</TD><TD>
Some cvs commands require a working directory to operate; some require
a repository. Also, some commands change the repository, some change the
working directory, and some change nothing.
</TD></TR><TR><TD>
Synonyms
</TD><TD>
Many commands have synonyms, which you may find easier to remember (or
type) than the principal name.
</TD></TR></TABLE>
<A NAME="PAGENUM-96"><P>Page 96</P></A>
<!-- CODE SNIP //-->
<PRE>
add [_k kflag][_m `message'] files...
</PRE>
<!-- END CODE SNIP //-->
<TABLE>
<TR><TD>
Requires:
</TD><TD>
Repository, working directory
</TD></TR><TR><TD>
Changes:
</TD><TD>
Working directory
</TD></TR><TR><TD>
Synonym:
</TD><TD>
new
</TD></TR></TABLE>
<P>Use the add command to create a new file or directory in the RCS source repository. The files or directories specified
with add must already exist in the current directory (which must have been created with the checkout command). To add a
whole new directory hierarchy to the source repository (for example, files received from a third-party vendor), use the
cvs import command instead.
</P>
<P>If the argument to cvs add refers to an immediate subdirectory, the directory is created at the correct place in the RCS
source repository, and the necessary cvs administration files are created in your working directory. If the directory already exists
in the source repository, cvs add still creates the administration files in your version of the directory. This allows you to use
cvs add to add a particular directory to your private sources even if someone else created that directory after your checkout of
the sources. You can do the following:
</P>
<!-- CODE SNIP //-->
<PRE>
example% mkdir new_directory
example% cvs add new_directory
example% cvs update new_directory
</PRE>
<!-- END CODE SNIP //-->
<P>An alternate approach using cvs update might be:</P>
<!-- CODE SNIP //-->
<PRE>
example% cvs update -d new_directory
</PRE>
<!-- END CODE SNIP //-->
<P>(To add any available new directories to your working directory, it's probably simpler to use
cvs checkout or cvs update -d.)
</P>
<P>The added files are not placed in the RCS source repository until you use
cvs commit to make the change permanent. Doing a cvs
add on a file that was removed with the cvs remove command will resurrect the file, if no
cvs commit command intervened.
</P>
<P>You will have the opportunity to specify a logging message, as usual, when you use
cvs commit to make the new file permanent. If you'd like to have another logging message associated with just creation of the file (for example, to describe
the file's purpose), you can specify it with the _m
message option to the add command.
</P>
<P>The -k kflag option specifies the default way that this file will be checked out. The
kflag argument is stored in the RCS file and can be changed with
cvs admin. Specifying -ko is useful for checking in binaries that shouldn't have the RCS
id strings expanded.
</P>
<!-- CODE SNIP //-->
<PRE>
admin [rcs-options] files...
</PRE>
<!-- END CODE SNIP //-->
<TABLE>
<TR><TD>
Requires:
</TD><TD>
Repository, working directory
</TD></TR><TR><TD>
Changes:
</TD><TD>
Repository
</TD></TR><TR><TD>
Synonym:
</TD><TD>
rcs
</TD></TR></TABLE>
<P>
This is the cvs interface to assorted administrative RCS facilities, documented in
rcs(1). cvs admin simply passes all its options and arguments to the
rcs command; it does no filtering or other processing. This command does work
recursively, however, so extreme care should be used.
</P>
<!-- CODE SNIP //-->
<PRE>
checkout [options] modules...
</PRE>
<!-- END CODE SNIP //-->
<TABLE>
<TR><TD>
Requires:
</TD><TD>
Repository
</TD></TR><TR><TD>
Changes:
</TD><TD>
Working directory
</TD></TR><TR><TD>
Synonyms:
</TD><TD>
co, get
</TD></TR></TABLE>
<P>Make a working directory containing copies of the source files specified by modules. You must execute
cvs checkout before using most of the other cvs commands, since most of them operate on your working directory.
</P>
<P>modules are either symbolic names [themselves defined as the module
modules in the source repository; see cvs(5)] for
some collection of source directories and files, or paths to directories or files in the repository.
</P>
<P>Depending on the modules you specify, checkout may recursively create directories and populate them with the
appropriate source files. You can then edit these source files at any time (regardless of whether other software developers are editing
their
</P>
<P><CENTER>
<a href="0093-0094.html">Previous</A> | <a href="../ewtoc.html">Table of Contents</A> | <a href="0097-0097.html">Next</A></CENTER></P>
</td>
</tr>
</table>
<!-- begin footer information -->
</body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -