(cvsclient.info.gz) Response pathnames

(cvsclient.info.gz) Response intro

 
 5.10 The "pathname" in responses
 ================================
 
 Many of the responses contain something called PATHNAME.  The name is
 somewhat misleading; it actually indicates a pair of pathnames.  First,
 a local directory name relative to the directory in which the command
 was given (i.e. the last `Directory' before the command).  Then a
 linefeed and a repository name.  Then a slash and the filename (without
 a `,v' ending).
 
    The repository name may be absolute or relative to the PATHNAME sent
 with the `Root' request.  If absolute, the repository name must begin
 with the PATHNAME sent with the `Root' request.  Relative or absolute,
 the repository name must specify a path underneath the `Root' PATHNAME.
 
    For example, for a file `i386.mh' which is in the local directory
 `gas.clean/config' and for which the repository name is
 `devo/gas/config':
 
      gas.clean/config/
      devo/gas/config/i386.mh
 
    If the server wants to tell the client to create a directory, then it
 merely uses the directory in any response, as described above, and the
 client should create the directory if it does not exist.  Note that this
 should only be done one directory at a time, in order to permit the
 client to correctly store the repository for each directory.  Servers
 can use requests such as `Clear-sticky', `Clear-static-directory', or
 any other requests, to create directories.
 
    Some server implementations may poorly distinguish between a
 directory which should not exist and a directory which contains no
 files; in order to refrain from creating empty directories a client
 should both send the `-P' option to `update' or `co', and should also
 detect the case in which the server asks to create a directory but not
 any files within it (in that case the client should remove the
 directory or refrain from creating it in the first place).  Note that
 servers could clean this up greatly by only telling the client to
 create directories if the directory in question should exist, but until
 servers do this, clients will need to offer the `-P' behavior described
 above.

Info Catalog

(cvsclient.info.gz) Response intro

(cvsclient.info.gz) Protocol

(cvsclient.info.gz) Responses

automatically generated byinfo2html