Lines Matching full:directory
37 CVS to @dfn{check out} a @dfn{working directory} from the repository, to
45 directory, run the CVS @dfn{client} program. To perform operations
421 In most contexts, @samp{/} is used to separate directory and file
538 Note that @var{pathname} is a local directory and @emph{not} a fully
561 @item Directory @var{local-directory} \n
563 Tell the server what directory to use. The @var{repository} should be a
564 directory name from a previous server response. Note that
567 @code{Directory} for each directory in which there will be an
568 @code{Entry} or @code{Modified}, and then a final @code{Directory}
569 for the original directory, then the command.
570 The @var{local-directory} is relative to
572 @code{Directory} which is sent before the command);
574 @var{local-directory}.
577 @var{local-directory}. Suppose that there is a module defined by
585 directory. Then an initial check out could proceed like this:
591 C: Directory .
603 directory to check out into. The second one, ending in @file{1dir/},
604 indicates the directory to pass back to the server in a subsequent
605 @code{Directory} request. For example, a subsequent @code{update}
609 C: Directory moddir
615 For a given @var{local-directory}, the repository will be the same for
618 repository along with the sources for each @var{local-directory}, use
619 that same setting whenever operating on that @var{local-directory}, and
620 not update the setting as long as the @var{local-directory} exists.
622 A client is free to rename a @var{local-directory} at any time (for
624 that the server supplies a @var{local-directory} to the client, as noted
625 above, this is only the default place to put the directory. Of course,
626 the various @code{Directory} requests for a single command (for example,
627 @code{update} or @code{ci} request) should name a particular directory
628 with the same @var{local-directory}.
630 Each @code{Directory} request specifies a brand-new
631 @var{local-directory} and @var{repository}; that is,
632 @var{local-directory} and @var{repository} are never relative to paths
633 specified in any previous @code{Directory} request.
636 working directory which has been checked out from multiple places in the
641 C: Directory dir1
645 C: Directory dir2
649 C: Directory dir3/subdir3
658 is actually checked out into @code{dir3/subdir3}, meaning that directory
665 mentioned in @code{Directory} requests.
670 a directory has been mentioned in a @code{Directory} request.
672 @code{dir2}, but would skip @code{dir3} because that directory was not
673 specifically mentioned in a @code{Directory} request. A functional
679 C: Directory dir1
683 C: Directory dir2
687 C: Directory dir3
690 C: Directory dir3/subdir3
696 Note the extra @code{Directory dir3} request. It might be better to use
697 @code{Emptydir} as the repository for the @code{dir3} directory, but the
701 @code{Directory} arguments. In order for a subdirectory to be
709 C: Directory dir3/subdir3
712 C: Directory dir3
719 administration files for a given directory at the time of the
720 @code{Directory} request. It also tries to register the directory with
722 @code{dir3/subdir3} is created, the physical directory for @code{dir3}
731 directory which @code{Directory} requests are relative to will be
733 @code{Directory} request for @file{../../foo}, it must send a
735 @code{Max-dotdot} must be sent before the first @code{Directory}
738 @item Static-directory \n
739 Response expected: no. Tell the server that the directory most recently
740 specified with @code{Directory} should not have
743 by the @code{Set-static-directory} and @code{Clear-static-directory}
747 Response expected: no. Tell the server that the directory most recently
748 specified with @code{Directory} has a sticky tag or date @var{tagspec}.
754 The server should remember @code{Static-directory} and @code{Sticky}
755 requests for a particular directory; the client need not resend them
756 each time it sends a @code{Directory} request for a given directory.
761 Response expected: no. Tell the server that the directory most recently
762 specified with @code{Directory} has a checkin program @var{program}.
767 Response expected: no. Tell the server that the directory most recently
768 specified with @code{Directory} has an update program @var{program}.
775 directory most recently specified with @code{Directory}. If the user
776 is operating on only some files in a directory, @code{Entry} requests
780 lost (does not exist in the working directory). If both @code{Entry}
821 a file within the most recent directory sent with @code{Directory}; it
823 the user is operating on only some files in a directory, only those
853 directory, and thus should not be sending either @code{Modified} or
864 modified in the checked out directory. The @var{filename} is
865 a file within the most recent directory sent with @code{Directory}; it
880 The @var{filename} is a file within the most recent directory sent with
881 @code{Directory}; it must not contain @samp{/}.
899 directory where the edit or unedit took place. @var{watches} are the
924 by the directory and filename. @var{filename} must not contain
925 @samp{/}; it needs to be a file in the directory named by the most
926 recent @code{Directory} request.
941 filenames in the working directory and filenames in the protocol), but
1028 rdiff; the latter do not access the working directory and thus have no
1045 working directory. Now suppose the client already has this module
1049 directories under the current directory, which could be unnecessarily
1055 @c out a fresh directory? Not that the CVS client does this, or that
1065 C: Directory .
1072 and then it knows to check the @file{1dir} directory and send
1074 directory.
1086 previous @code{Argument}, @code{Directory}, @code{Entry}, or
1088 last @code{Directory} sent specifies the working directory at the time
1095 any previous @code{Directory}, @code{Entry}, or @code{Modified}
1096 requests, if they have been sent. The last @code{Directory} sent
1097 specifies the working directory at the time of the operation. Also uses
1145 previous @code{Argument}, @code{Directory}, @code{Entry}, or
1149 seeing what directory names the server sends back in its responses, and
1154 previous @code{Argument}, @code{Directory}, @code{Entry}, or
1171 should not send @code{Directory}, @code{Entry}, or @code{Modified}
1178 directory and @emph{not} a fully qualified @code{CVSROOT} variable.
1183 uses any previous @code{Argument}, @code{Directory}, @code{Entry},
1185 last @code{Directory} sent specifies the working directory at the time
1192 uses any previous @code{Argument}, @code{Directory}, @code{Entry}, or
1194 last @code{Directory} sent specifies the working directory at the time
1196 @code{Directory} request is ignored (it merely must point somewhere
1204 Response expected: yes. Add a file or directory. This uses any
1205 previous @code{Argument}, @code{Directory}, @code{Entry}, or
1207 last @code{Directory} sent specifies the working directory at the time
1210 To add a directory, send the directory to be added using
1211 @code{Directory} and @code{Argument} requests. For example:
1217 C: Directory nsdir
1219 C: Directory .
1222 S: M Directory /u/cvsroot/1dir/nsdir added to the repository
1227 particular way that the directory has been successfully added. The
1228 client is supposed to just assume that the directory has been added and
1229 update its records accordingly. Note also that adding a directory is
1237 C: Directory .
1269 all @code{Directory} requests for @code{add} (except those used to add
1271 @var{local-directory}. Specifying another string for
1272 @var{local-directory} may not get an error, but it will get you strange
1277 previous @code{Argument}, @code{Directory}, @code{Entry}, or
1279 last @code{Directory} sent specifies the working directory at the time
1299 @code{Directory}, @code{Entry}, or @code{Modified}
1300 requests, if they have been sent. The last @code{Directory} sent
1301 specifies the working directory at the time of the operation.
1377 they change the status of a file in the working directory in some way.
1394 pathnames. First, a local directory name
1395 relative to the directory in which the command was given (i.e. the last
1396 @code{Directory} before the command). Then a linefeed and a repository
1400 which is in the local directory @file{gas.clean/config} and for which
1408 If the server wants to tell the client to create a directory, then it
1409 merely uses the directory in any response, as described above, and the
1410 client should create the directory if it does not exist. Note that this
1411 should only be done one directory at a time, in order to permit the
1412 client to correctly store the repository for each directory. Servers
1414 @code{Clear-static-directory}, or any other requests, to create
1417 @c each directory, and cannot be correctly deduced from, say, the most
1418 @c deeply nested directory.
1421 implementations may poorly distinguish between a directory which should
1422 not exist and a directory which contains no files; in order to refrain
1425 which the server asks to create a directory but not any files within it
1426 (in that case the client should remove the directory or refrain from
1429 directory in question should exist, but until servers do this, clients
1458 being updated it will be up to date. If any directory in pathname does
1468 a file in the working directory, but not one for which @code{Entry},
1471 there is a file in the working directory whose name differs from the one
1571 @var{newname} in the same directory where it already is. This does not
1589 @item Set-static-directory @var{pathname} \n
1591 it should then send back to the server in a @code{Static-directory}
1592 request whenever the directory is operated on. @var{pathname} ends in a
1593 slash; its purpose is to specify a directory, not a file within a
1594 directory.
1596 @item Clear-static-directory @var{pathname} \n
1597 Like @code{Set-static-directory}, but clear, not set, the flag.
1603 specify a directory, not a file within a directory. The client should
1615 specify a directory, not a file within a directory. Tell the client to
1637 Return a file or directory
1643 contains the @samp{-d} option, it will be the directory specified with
1793 being updated relative to the directory in which the command is
1794 occurring (that is, the last @code{Directory} request which is sent
1846 S: Valid-requests Root Directory Entry Modified Argument Argumentx ci co
1852 working directory. Therefore it first expands the @code{supermunger}
1854 directory rather than a module.
1855 @c Why does it send Directory here? The description of expand-modules
1857 @c Directory and similar requests sent previously.
1861 C: Directory .
1867 directory @code{supermunger} (the simplest case):
1874 The client then proceeds to check out the directory. The fact that it
1875 sends only a single @code{Directory} request which specifies @samp{.}
1876 for the working directory means that there is not already a
1877 @code{supermunger} directory on the client.
1883 C: Directory .
1890 @code{Clear-static-directory} requests are sent by the current
1892 settings to be clear when a directory is newly created.
1897 S: Clear-static-directory supermunger/
1926 It also sends information about the contents of the working directory,
1928 changed into the @file{supermunger} directory before executing this
1929 command; the top level directory is a user-visible concept because the
1931 relative to that directory.
1932 @c We are waving our hands about the order of the requests. "Directory"
1937 C: Directory .
1975 @code{Directory}, @code{Entry}, @code{Modified}, @code{Unchanged},
1991 There was a @code{Repository} request which was like @code{Directory}
1992 except it only provided @var{repository}, and the local directory was
1997 working directory, and the meaning of sending @code{Entries} without