checkcomb - Checks if selected versions of RCS files in one RCS
      library can be combined into another RCS library.


      checkcomb [options] files RCS_dest


      The checkcomb command checks if specified versions of files placed in
      the RCS source library can be combined into the RCS_dest library. This
      check must be done before any combining of the RCS libraries can be

      The command checks so there is no later version of each file in the
      RCS_dest library than in the RCS source library. For example, it is
      illegal to combine file1, if the version in the source directory is
      1.6, but the one in the RCS_dest library is 1.7. (A file is combined
      with the same version as in the RCS source library).

      A library is illegal to combine, if any file is illegal to combine. If
      a library is illegal to combine, it can if necessary be combined into
      a branch. See rcscomb(1).

      The command produces a list, checkcomb.lis, placed in the source
      directory. This list is used when the directory is combined, and must
      not be removed. After the combining the list is removed.

           Specifies which files will be checked. All specified files that
           match values are checked. Normally all files from the source RCS
           directory are taken.

           Specifies the RCS library where the RCS files are checked to.

      If no option is specified then the latest versions are checked.

           Select the latest version of files whose number is less than or
           equal to rev. If rev indicates a branch rather than a version,
           the latest version on that branch is retrieved. If -r rev is
           omitted, the latest version on the default branch is retrieved.
           If rev is $, the command determines the version number from
           keyword values in the working file. Otherwise, a version is
           composed of one or more numeric or symbolic fields separated by

           Select the latest version on the selected branch whose state is
           set to state.

           Select the latest version on the selected branch which was
           checked in by the user with login name login.

           Select files specified by the suffixes for RCS files. A nonempty
           suffix matches any pathname ending in the suffix. An empty suffix
           matches any pathname of the form RCS/file or path/RCS/file. The
           -x option can specify a list of suffixes separated by /. For
           example, -x ,v/ specifies two suffixes: ,v and the empty suffix.
           If two or more suffixes are specified, they are tried in order
           when looking for an RCS file; the first one that works is used
           for that file. If no RCS file is found but an RCS file can be
           created, the suffixes are tried in order to determine the new RCS
           file's name. The default for suffixes is installation-dependent;
           normally it is ,v/ for hosts like Unix that permit commas in file
           names, and is empty (i.e. just the empty suffix) for other hosts.

           Select the latest version on the selected branch whose checkin
           date/time is less than or equal to date. The date and time may be
           given in free format. The time zone LT stands for local time;
           other common time zone names are understood. For more details see
           the co(1) command.

      -v   Lists all checked files, and the checked versions of each file.


      checkcomb -rR1_0_0  /rel/RCS

      checks if all the file versions specified by the symbolic name R1_0_0
      from the RCS library placed in the current directory can be combined
      into the /rel/RCS directory.

      checkcomb  /rel/RCS

      takes the latest versions of all the files from the original RCS
      library (in current directory) and checks if they can be combined into
      the /rel/RCS.


      rcscomb(1), s_combine(1)


      Elisabet de Waal