1<div id="checkout-options"></div> 2<div class="header"> 3<p> 4Next: [[cvs: checkout examples#checkout examples|checkout examples]], Up: [[cvs: checkout--Check out sources for editing#checkout—Check out sources for editing|checkout]] |[[cvs: Index#SEC_Contents|Contents]]||[[cvs: Index#Index|Index]]|</p> 5</div> 6 7---- 8 9<div id="checkout-options-1"></div> 10==== checkout options ==== 11 12These standard options are supported by <code>checkout</code> 13(see [[cvs: Common command options#Common command options|Common options]], for a complete description of 14them): 15 16;<code>-D <var>date</var></code> 17: Use the most recent revision no later than <var>date</var>. This option is sticky, and implies ‘<code>-P</code>’. See [[cvs: Sticky tags#Sticky tags|Sticky tags]], for more information on sticky tags/dates. 18 19;<code>-f</code> 20: Only useful with the ‘<code>-D <var>date</var></code>’ or ‘<code>-r <var>tag</var></code>’ flags. If no matching revision is found, retrieve the most recent revision (instead of ignoring the file). 21 22;<code>-k <var>kflag</var></code> 23: Process keywords according to <var>kflag</var>. See [[cvs: Keyword substitution#Keyword substitution|Keyword substitution]]. This option is sticky; future updates of this file in this working directory will use the same <var>kflag</var>. The <code>status</code> command can be viewed to see the sticky options. See [[cvs: Quick reference to CVS commands#Quick reference to CVS commands|Invoking CVS]], for more information on the <code>status</code> command. 24 25;<code>-l</code> 26: Local; run only in current working directory. 27 28;<code>-n</code> 29: Do not run any checkout program (as specified with the ‘<code>-o</code>’ option in the modules file; see [[cvs: The modules file#The modules file|modules]]). 30 31;<code>-P</code> 32: Prune empty directories. See [[cvs: Moving and renaming directories#Moving and renaming directories|Moving directories]]. 33 34;<code>-p</code> 35: Pipe files to the standard output. 36 37;<code>-R</code> 38: Checkout directories recursively. This option is on by default. 39 40;<code>-r <var>tag</var></code> 41: Use revision <var>tag</var>. This option is sticky, and implies ‘<code>-P</code>’. See [[cvs: Sticky tags#Sticky tags|Sticky tags]], for more information on sticky tags/dates. 42 43In addition to those, you can use these special command 44options with <code>checkout</code>: 45 46;<code>-A</code> 47: Reset any sticky tags, dates, or ‘<code>-k</code>’ options. See [[cvs: Sticky tags#Sticky tags|Sticky tags]], for more information on sticky tags/dates. 48 49;<code>-c</code> 50: Copy the module file, sorted, to the standard output, instead of creating or modifying any files or directories in your working directory. 51 52;<code>-d <var>dir</var></code> 53: Create a directory called <var>dir</var> for the working files, instead of using the module name. In general, using this flag is equivalent to using ‘<code>mkdir <var>dir</var>; cd <var>dir</var></code>’ followed by the checkout command without the ‘<code>-d</code>’ flag. 54 55: There is an important exception, however. It is very convenient when checking out a single item to have the output appear in a directory that doesn’t contain empty intermediate directories. In this case ''only'', <small>CVS</small> tries to “shorten” pathnames to avoid those empty directories. 56 57: For example, given a module ‘<code>foo</code>’ that contains the file ‘<code>bar.c</code>’, the command ‘<code>cvs co -d dir foo</code>’ will create directory ‘<code>dir</code>’ and place ‘<code>bar.c</code>’ inside. Similarly, given a module ‘<code>bar</code>’ which has subdirectory ‘<code>baz</code>’ wherein there is a file ‘<code>quux.c</code>’, the command ‘<code>cvs co -d dir bar/baz</code>’ will create directory ‘<code>dir</code>’ and place ‘<code>quux.c</code>’ inside. 58 59: Using the ‘<code>-N</code>’ flag will defeat this behavior. Given the same module definitions above, ‘<code>cvs co -N -d dir foo</code>’ will create directories ‘<code>dir/foo</code>’ and place ‘<code>bar.c</code>’ inside, while ‘<code>cvs co -N -d dir bar/baz</code>’ will create directories ‘<code>dir/bar/baz</code>’ and place ‘<code>quux.c</code>’ inside. 60 61;<code>-j <var>tag</var></code> 62: With two ‘<code>-j</code>’ options, merge changes from the revision specified with the first ‘<code>-j</code>’ option to the revision specified with the second ‘<code>j</code>’ option, into the working directory. 63 64: With one ‘<code>-j</code>’ option, merge changes from the ancestor revision to the revision specified with the ‘<code>-j</code>’ option, into the working directory. The ancestor revision is the common ancestor of the revision which the working directory is based on, and the revision specified in the ‘<code>-j</code>’ option. 65 66: In addition, each -j option can contain an optional date specification which, when used with branches, can limit the chosen revision to one within a specific date. An optional date is specified by adding a colon (:) to the tag: ‘<code>-j<var>Symbolic_Tag</var>:<var>Date_Specifier</var></code>’. 67 68: See [[cvs: Branching and merging#Branching and merging|Branching and merging]]. 69 70;<code>-N</code> 71: Only useful together with ‘<code>-d <var>dir</var></code>’. With this option, <small>CVS</small> will not “shorten” module paths in your working directory when you check out a single module. See the ‘<code>-d</code>’ flag for examples and a discussion. 72 73;<code>-s</code> 74: Like ‘<code>-c</code>’, but include the status of all modules, and sort it by the status string. See [[cvs: The modules file#The modules file|modules]], for info about the ‘<code>-s</code>’ option that is used inside the modules file to set the module status. 75 76 77---- 78 79<div class="header"> 80<p> 81Next: [[cvs: checkout examples#checkout examples|checkout examples]], Up: [[cvs: checkout--Check out sources for editing#checkout—Check out sources for editing|checkout]] |[[cvs: Index#SEC_Contents|Contents]]||[[cvs: Index#Index|Index]]|</p> 82</div> 83This document was generated on <i>a sunny day</i> using [http://www.nongnu.org/texi2html/ <i>texi2html</i>]. 84