sccs \- front end for the
] command [ flags ] [ args ]
that help them mesh more cleanly
It also includes the capability to run
``set user id'' to another user
to provide additional protection.
is normally modified to be prepended
Flags to be interpreted by the
program must be before the
Flags to be passed to the actual
These flags are specific to the command
and are discussed in the documentation for that command.
several ``pseudo-commands'' can be issued.
Equivalent to ``get \-e''.
Perform a delta on the named files
and then get new versions.
The new versions will have id keywords expanded,
and will not be editable.
The \-m, \-p, \-r, \-s, and \-y flags
and the \-b, \-c, \-e, \-i, \-k, \-l, \-s, and \-x flags
Equivalent to ``delget'' except that the
``get'' phase includes the ``\-e'' flag.
This option is useful for making a ``checkpoint''
of your current editing phase.
The same flags will be passed to delta
and all the flags listed for ``get''
taking the initial contents from the file of the same name.
Any flags to ``admin'' are accepted.
If the creation is successful,
the files are renamed with a comma on the front.
These should be removed when you are convinced that
files have been created successfully.
This command essentially removes the named delta,
but leaves you with a copy of the delta
with the changes that were in it.
It is useful for fixing small compiler bugs, etc.
Since it doesn't leave audit trails,
it should be used carefully.
This routine removes everything from the current directory
that can be recreated from SCCS files.
It will not remove any files being edited.
flag is given, branches are ignored in the determination
of whether they are being edited;
this is dangerous if you are keeping the branches in the
This is the opposite of an ``edit''
It should be used with extreme caution,
since any changes you made since the get
will be irretrievably lost.
Gives a listing of all files being edited.
\s-1SID\s0's with two or fewer components)
(with an optional argument)
then only files being edited by you
except that nothing is printed if nothing is being edited,
and a non-zero exit status is returned if anything
The intent is to have this included in an ``install''
to insure that everything is included into the
before a version is installed.
Gives a newline-separated list
of the files being edited
Gives a ``diff'' listing between the current version of the
program(s) you have out for editing and the versions
This command prints out verbose information
rather than as whatever effective user
flag gives a root directory for the
The default is the current directory.
flag defines the pathname of the directory
argument is prepended to the entire pathname
argument is inserted before the final component of the
``sccs \-d/x \-py get a/b''
The intent here is to create aliases such as
``alias syssccs sccs -d/usr/src''
``syssccs get cmd/who.c''.
Also, if the environment variable
its value is used to determine the
If it begins with a slash,
the home directory of a user of that name
is examined for a subdirectory ``src'' or ``source''.
If such a directory is found,
Certain commands (such as
cannot be run ``set user id'' by all users,
since this would allow anyone to change the authorizations.
These commands are always run as the real user.
To get a file for editing,
To get a file from another directory:
sccs \-p/usr/src/sccs/s. get cc.c
sccs get /usr/src/sccs/s.cc.c
To make a delta of a large number of files
in the current directory:
To get a list of files being edited that are not on branches:
To delta everything being edited by you:
sccs delta \`sccs tell \-u\`
In a makefile, to get source files
file if it does not already exist:
SRCS = <list of source files>
An Introduction to the Source Code Control System
It should be able to take directory arguments on pseudo-commands
Since it is not yet clear
what this program should do,
it should not be considered
a stable program product.