Lines Matching full:directory
19 Note that PATHNAME is a local directory and _not_ a fully
41 `Directory LOCAL-DIRECTORY \n'
43 server what directory to use. The REPOSITORY should be a
44 directory name from a previous server response. Note that this
46 and the other commands; normal usage is to send `Directory' for
47 each directory in which there will be an `Entry' or `Modified',
48 and then a final `Directory' for the original directory, then the
49 command. The LOCAL-DIRECTORY is relative to the top level at
50 which the command is occurring (i.e. the last `Directory' which is
52 be sent for LOCAL-DIRECTORY.
55 LOCAL-DIRECTORY. Suppose that there is a module defined by
60 repository and check it out to `moddir' in the working directory.
66 C: Directory .
76 The first one, `moddir/', indicates the working directory to check
78 directory to pass back to the server in a subsequent `Directory'
82 C: Directory moddir
87 For a given LOCAL-DIRECTORY, the repository will be the same for
90 repository along with the sources for each LOCAL-DIRECTORY, use
91 that same setting whenever operating on that LOCAL-DIRECTORY, and
92 not update the setting as long as the LOCAL-DIRECTORY exists.
94 A client is free to rename a LOCAL-DIRECTORY at any time (for
96 true that the server supplies a LOCAL-DIRECTORY to the client, as
97 noted above, this is only the default place to put the directory.
98 Of course, the various `Directory' requests for a single command
100 directory with the same LOCAL-DIRECTORY.
102 Each `Directory' request specifies a brand-new LOCAL-DIRECTORY and
103 REPOSITORY; that is, LOCAL-DIRECTORY and REPOSITORY are never
104 relative to paths specified in any previous `Directory' request.
107 working directory which has been checked out from multiple places
111 C: Directory dir1
115 C: Directory dir2
119 C: Directory dir3/subdir3
127 is actually checked out into `dir3/subdir3', meaning that directory
134 specifically mentioned in `Directory' requests.
139 occurs if a directory has been mentioned in a `Directory' request.
141 `dir2', but would skip `dir3' because that directory was not
142 specifically mentioned in a `Directory' request. A functional
147 C: Directory dir1
151 C: Directory dir2
155 C: Directory dir3
158 C: Directory dir3/subdir3
163 Note the extra `Directory dir3' request. It might be better to use
164 `Emptydir' as the repository for the `dir3' directory, but the
168 ordering of `Directory' arguments. In order for a subdirectory to
175 C: Directory dir3/subdir3
178 C: Directory dir3
184 administration files for a given directory at the time of the
185 `Directory' request. It also tries to register the directory with
187 time `dir3/subdir3' is created, the physical directory for `dir3'
195 directories above the directory which `Directory' requests are
197 planning to use a `Directory' request for `../../foo', it must
199 `Max-dotdot' must be sent before the first `Directory' request.
201 `Static-directory \n'
202 Response expected: no. Tell the server that the directory most
203 recently specified with `Directory' should not have additional
206 the `Set-static-directory' and `Clear-static-directory' responses.
209 Response expected: no. Tell the server that the directory most
210 recently specified with `Directory' has a sticky tag or date
216 The server should remember `Static-directory' and `Sticky'
217 requests for a particular directory; the client need not resend
218 them each time it sends a `Directory' request for a given
219 directory. However, the server is not obliged to remember them
223 Response expected: no. Tell the server that the directory most
224 recently specified with `Directory' has a checkin program PROGRAM.
229 Response expected: no. Tell the server that the directory most
230 recently specified with `Directory' has an update program PROGRAM.
237 to the directory most recently specified with `Directory'. If the
238 user is operating on only some files in a directory, `Entry'
242 directory). If both `Entry' and one of `Modified', `Is-modified',
282 file. FILENAME is a file within the most recent directory sent
283 with `Directory'; it must not contain `/'. If the user is
284 operating on only some files in a directory, only those files need
313 directory, and thus should not be sending either `Modified' or
322 modified in the checked out directory. The FILENAME is a file
323 within the most recent directory sent with `Directory'; it must
337 the most recent directory sent with `Directory'; it must not
348 pathname of the working directory where the edit or unedit took
373 the directory and filename. FILENAME must not contain `/'; it
374 needs to be a file in the directory named by the most recent
375 `Directory' request.
389 filenames in the working directory and filenames in the protocol),
471 not rtag or rdiff; the latter do not access the working directory
486 directory. Now suppose the client already has this module checked
490 directories under the current directory, which could be
501 C: Directory .
507 and then it knows to check the `1dir' directory and send requests
508 such as `Entry' and `Modified' for the files in that directory.
520 previous `Argument', `Directory', `Entry', or `Modified' requests,
521 if they have been sent. The last `Directory' sent specifies the
522 working directory at the time of the operation. No provision is
528 This uses any previous `Directory', `Entry', or `Modified'
529 requests, if they have been sent. The last `Directory' sent
530 specifies the working directory at the time of the operation.
578 any previous `Argument', `Directory', `Entry', or `Modified'
582 seeing what directory names the server sends back in its
587 any previous `Argument', `Directory', `Entry', or `Modified'
604 should not send `Directory', `Entry', or `Modified' requests for
610 repository ROOT-NAME. Note that ROOT-NAME is a local directory
616 uses any previous `Argument', `Directory', `Entry', or `Modified'
617 requests, if they have been sent. The last `Directory' sent
618 specifies the working directory at the time of the operation. The
625 uses any previous `Argument', `Directory', `Entry', or `Modified'
626 requests, if they have been sent. The last `Directory' sent
627 specifies the working directory at the time of the operation -
628 unlike most commands, the repository field of each `Directory'
637 Response expected: yes. Add a file or directory. This uses any
638 previous `Argument', `Directory', `Entry', or `Modified' requests,
639 if they have been sent. The last `Directory' sent specifies the
640 working directory at the time of the operation.
642 To add a directory, send the directory to be added using
643 `Directory' and `Argument' requests. For example:
648 C: Directory nsdir
650 C: Directory .
653 S: M Directory /u/cvsroot/1dir/nsdir added to the repository
657 any particular way that the directory has been successfully added.
658 The client is supposed to just assume that the directory has been
660 directory is immediate; it does not wait until a `ci' request as
667 C: Directory .
696 with the older servers is to ensure that all `Directory' requests
698 above), use `.' for LOCAL-DIRECTORY. Specifying another string for
699 LOCAL-DIRECTORY may not get an error, but it will get you strange
704 `Argument', `Directory', `Entry', or `Modified' requests, if they
705 have been sent. The last `Directory' sent specifies the working
706 directory at the time of the operation.
724 respectively. This uses any previous `Argument', `Directory',
726 `Directory' sent specifies the working directory at the time of
803 working directory in some way. The responses `Mode', `Mod-time', and
820 First, a local directory name relative to the directory in which the
821 command was given (i.e. the last `Directory' before the command). Then
824 the local directory `gas.clean/config' and for which the repository is
830 If the server wants to tell the client to create a directory, then it
831 merely uses the directory in any response, as described above, and the
832 client should create the directory if it does not exist. Note that this
833 should only be done one directory at a time, in order to permit the
834 client to correctly store the repository for each directory. Servers
835 can use requests such as `Clear-sticky', `Clear-static-directory', or
839 directory which should not exist and a directory which contains no
842 detect the case in which the server asks to create a directory but not
844 directory or refrain from creating it in the first place). Note that
846 create directories if the directory in question should exist, but until