This is cssc.info, produced by makeinfo version 4.1 from cssc.texi. INFO-DIR-SECTION Miscellaneous START-INFO-DIR-ENTRY * cssc: (cssc). The GNU work-alike replacement for SCCS. END-INFO-DIR-ENTRY This file documents the the GNU `cssc' package for working with SCCS files. Copyright (C) 1997,1998,1999,2000,2001,2002 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Foundation.  File: cssc.info, Node: BSD Code, Next: Glossary, Prev: Copying, Up: Top BSD Code ******** The program `sccs', its source code, and its accompanying documentation are covered by the following license:- Copyright (C) 1998, 1999 Free Software Foundation, Inc. All rights reserved. Copyright (c) 1980, 1993 The Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The original version of the copyright notice above dates from 1993, as you can see. However, since that time a change has been made to the BSD license by UCB itself. This change is described on the following letter, which is available on the BSD FTP site in the file `README.Impt.License.Change' :- July 22, 1999 To All Licensees, Distributors of Any Version of BSD: As you know, certain of the Berkeley Software Distribution ("BSD") source code files require that further distributions of products containing all or portions of the software, acknowledge within their advertising materials that such products contain software developed by UC Berkeley and its contributors. Specifically, the provision reads: " * 3. All advertising materials mentioning features or use of this software * must display the following acknowledgement: * This product includes software developed by the University of * California, Berkeley and its contributors." Effective immediately, licensees and distributors are no longer required to include the acknowledgement within advertising materials. Accordingly, the foregoing paragraph of those BSD Unix files containing it is hereby deleted in its entirety. William Hoskins Director, Office of Technology Licensing University of California, Berkeley This change has been made to the file `COPYING.bsd' which accompanies the BSD-derived code.  File: cssc.info, Node: Glossary, Next: Concept Index, Prev: BSD Code, Up: Top Glossary ******** archive In the context of SCCS and CSSC, This means the same as "history file". branch Notionally, a branch is a parallel or forked stream of changes. See "branching". body The actual data within the version-controlled file is called the "body", though this is also sometimes used to refer to that part of the SCCS history file that contains data from the body of the controlled file (that is, information _from_ the file as opposed to information _about_ the file). branching Multiple lines of development are called branches; a branch is created by editing a version of a file which already has a derived version (e.g. editing version 1.2 when version 1.3 already exists). checkin comment The `delta' program asks for a checkin comment; this is a comment which summarised the nature of the change which has just been made to the file. controlled file This is the (working copy of a) file which is version-controlled with an SCCS history file (that is, a file which is managed by SCCS or CSSC). d-file *Note Filenames::. delta Each revision of a controlled file, as recorded in an SCCS file is called a _delta_. This is also the name of the program used to check in such changes to the file. delta table This is the section of the SCCS file which records information about each change that has been made (other than the actual contents of the file at that version). excluded delta An excluded delta is one which was specified with the `-x' option to `get'. See *Note Options for `get': get options. g-file See _gotten file_. gotten file This is the working copy of the file; this is read-only unless the file has been checked out for editing. history file Also known as an SCCS archive or "s-file". When SCCS or CSSC is used to keep a historical record of previous versions of the contents of a file, the file in which this historical information is recorded is called the "history file". Sometimes there are known as "s-files" or "archives" (though "archive" is more often used in relation to the `ar' and `tar' utilities). ignored delta An ignored delta is one which was specified with the `-g' option to `delta'. *Note Options for `delta': delta options. included delta An included delta is one which was specified with the `-i' option to `get'. See *Note Options for `get': get options. keyword It is sometimes useful to include information in the gotten file about what its version number is and so on. Since this information changes with each revision of the file, it makes sense for SCCS (or CSSC) to keep track of this information and place it in the gotten file accordingly. If a file is checked out for editing, placeholders can be edited into the file which; these are later expanded when the file is checked out read-only. See *Note Keyword Substitution::. The same name is also sometimes used for the argument following the `-d' option for `prs'. See *Note Data Keywords for the `-d' option of `prs': Data Keywords. level The second component of the _SID_. MR number Modification Request numbers; if the `v' flag is set in the SCCS file, you will be prompted for "MR numbers" when you check in a new revision. These are not used internally by CSSC but may be used to link changes to external things (for example bug report numbers). *Note Options for `delta': delta options. p-file *Note Filenames::. q-file *Note Filenames::. release The first component of the _SID_. revision A _revision_ is a specific version of a file which is controlled with an SCCS history file. sequence number The "sequence number" is a decimal number used within the SCCS history file to identify a particular revision (or delta) of the file. These numbers are normally not user-visible (except in the output of `prt' and `prs'). These are sometimes referred to as a "seqno" in order to distinguish them from the fourth component of a SID. s-file The SCCS history file is sometimes referred to as the _s-file_. See also *Note Filenames::. SID Each revision of a file controlled with an SCCS history file is identified by a "SID". This is a series of numbers separated by dots. A complete SID always has either two components (for revisions which lie on the trunk) or four components (for revisions that lie on a branch). Examples are 1.1, 1.2 (which both lie on the trunk), 1.3.1.1, 1.3.1.2 (which both lie on a branch) and 1.3.2.1 (which lies on a different branch). The four components of the SID are, left to right, the _release_, the _level_, the _branch_ and the _sequence number_. See also _sequence number_, above. trunk The trunk consists of those deltas within a history file which do not lie on branches; trunk revisions have only two components in their SID. Normally these are the main sequence of changes to the file. x-file *Note Filenames::. z-file *Note Filenames::.  File: cssc.info, Node: Concept Index, Prev: Glossary, Up: Top Concept Index ************* * Menu: * @(#): what. * Activity summary: sact. * admin: admin. * Audit trailing: prs. * author: Overview. * Authorisation: admin. * backing out of changes: rmdel. * Binary files: admin. * branch: delta. * branches: branches. * Branching: Flags. * BSD <1>: BSD Code. * BSD: Overview. * Buffer overflows: Known Problems. * bug-fixing released code: branches. * bugs: Problems. * cdc: cdc. * censoring revisions: rmdel. * change delta commentary: cdc. * change summary: sccsdiff. * Change summary: prt. * changes, checking in: delta. * checking in changes: delta. * checking in new revisions: delta. * Checking sccs files for validity: val. * Checking the suite: Running the tests. * checking-out previous revisions: get. * checksum: admin. * comb: comb. * comment, changing: cdc. * Comments about CSSC: Problems. * committing changes: delta. * Concurrent editing: Flags. * Contributing test cases: Writing new test cases. * creating SCCS files: admin. * Cuddlier interface: sccs. * CVS: Overview. * deleting revisions: rmdel. * delta: delta. * delta comment, changing: cdc. * differences between revisions: sccsdiff. * docommand: docommand. * docommand function for test scripts: remove. * Dumping SCCS files: prs. * echo: echo_nonl. * ekko: echo_nonl. * Emacs: Interface. * Eric Allman: Overview. * Failures during multiple-file processing: Missing Features. * Flags: Flags. * forking: branches. * FreeBSD: BSD Code. * front-end tools: sccs. * g-file: get usage. * get: get. * help program: help. * identification string: what. * initial release number: admin. * initialising SCCS history files: admin. * Insecurity: Known Problems. * interface: Interface. * invoking: Invoking Programs. * Keyword Substitution: Keyword Substitution. * Known bugs: Missing Features. * level: delta. * locking revisions for update: get. * maintainer: Problems. * Making branches: Flags. * missing features: Incomplete. * Modification summary: prt. * modifying released code: branches. * mr-numbers: Modification Request Numbers. * MySC: Overview. * new versions: get. * obsolete releases: Flags. * Oops, it didn't compile: rmdel. * overview: Overview. * p-file: get options. * Pipes: Unemulated Features. * problems: Problems. * prs: prs. * prt: prt. * Questions about CSSC: Problems. * Race conditions: Known Problems. * release: delta. * Restricting access to history files: admin. * retrieving previous revisions: get. * Reverting to where you were before you broke it: unget. * Revision summary: prt. * revision summary: prs. * rmdel: rmdel. * Ross Ridge: Overview. * sact: sact. * sccs: sccs. * SCCS ID: what. * sccs-admin: admin. * sccs-cdc: cdc. * sccs-comb: comb. * sccs-delta: delta. * sccs-get: get. * sccs-help: help. * sccs-prs: prs. * sccs-prt: prt. * sccs-rmdel: rmdel. * sccs-sact: sact. * sccs-sccsdiff: sccsdiff. * sccs-unget: unget. * sccs-val: val. * sccsdiff: sccsdiff. * Security problems: Known Problems. * sequence: delta. * Setuid execution, why not to do it: Known Problems. * SID: delta. * Simultaneous editing: Flags. * success function for test scripts: success. * Suggestions for the improvement of CSSC: Problems. * Summary of changes to a history file: prt. * Summary of SCCS file: prs. * Sun Microsystems, Inc.: Year 2000 Issues. * test suite: Testing. * testing: Running the tests. * time travel: get options. * undoing revisions: rmdel. * unget: unget. * val: val. * validating SCCS files: val. * Validity checking: val. * VC-mode: Interface. * Version identifiers: Keyword Substitution. * Warning messages: Missing Features. * what: what. * Whodunit: prs. * X/Open: Year 2000 Issues. * Year 2000 <1>: Year 2000 Issues. * Year 2000 <2>: prt options. * Year 2000 <3>: Data Keywords. * Year 2000 <4>: prs options. * Year 2000 <5>: Keyword Substitution. * Year 2000: get options.