changeset(4)

NAME
changeset - format of an SCCS changeset file

DESCRIPTION

An SCCS changeset file is an ASCII file consisting of a list of entries that describe the state of a project-set under control of SCCSv6 or later.

The changeset file itself is under control of SCCS. SCCS works directly on the s.changeset file. There is no need to check out the related file content, as the deltas can be consructed without explicitely running the diff(1) program.

  Conventions

The following terms are used in this documentation:

project set
    A set of one or more files under control of SCCS that form a project.

project set home
    A directory that is above all files from the related project set. This directory holds a directory .sccs with project set related meta data such as the changeset file.

commit set
    A single set of changes into the repository for a project set.

committer
    The person who formed a commit set.

email address
    The email address used to identify a committer.

  File Format

Each entry in the changeset file describes the new state of a single file after it was modified, renamed, removed or restored in a related commit set.

Each entry in the changeset file ends in a newline character. If the file name from the related file contains a newline character, additional newlines may be in the related entry.

Each entry in the changeset file consists of six fields that are separated by a vertical line character (ASCII 0x7C). The vertical line character may not be part of the email address, it however may appear in the path name.

The following fields appear in the order of the following list:

    urand
        A unified pseudo random number that is used to help to identify single files across renames during the lifetime of the sccs history. The unified random number is unique to any file from the project set. See sccsfile(4) for a detailed description of the unified pseudo random number.

        The minimal length for the pseudo random number is thirteen hexadecimal characters. If the number could be represented with less digits, it is left filled with zeroes. This allows to have a unique length for this number until 2146 Sep 27 13:30:51 GMT.

    date-time
        A date-time specification in the form yyyymmDDHHMMSS as specified for the -c option of the get command. Only four or more digits are permitted to specify the year.

        All date-time values in the changeset file that belong to a single commit set are equal. Different changesets use different date-time values.

        In order to keep the date-time values monotonic, the time used for date-time is the time the changeset was added to the current repository. In case a changeset was imported from another repository, the date-time value may differ from the time the changeset was entered to the original repository.

    sid-sum
        The SID specific checksum for the related file. See sccsfile(4) for a detailed description of the SID specific checksums for a file.

    email
        The configured e-mail address for the committer.

    path length
        A decimal number representing the number of bytes in the path name not including the final newline character.

    path name
        The path name of the related file after the commit has been applied. The path name holds a relative path as seen from the project set home directory. As the path name is the last member in the lines of a changeset file, it may contain the vertical line character (ASCII 0x7C).

A typical entry in the changeset file may look like:

  0e31666e43286|20111205172040|45206|joerg@some.org|15|some/dir/file.c

SEE ALSO

sccs(1), sccs-admin(1), sccs-cdc(1), sccs-comb(1), sccs-delta(1), sccs-get(1), sccs-help(1), sccs-prs(1), sccs-prt(1), sccs-rmdel(1), sccs-sact(1), sccs-sccsdiff(1), sccs-unget(1), sccs-val(1), sccscvt(1), sccslog(1), bdiff(1), diff(1), what(1), sccsfile(4).

NOTES

BUGS

AUTHOR