.\" Copyright (c) 1983, 1990 The Regents of the University of California.
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" 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. 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.
.\" 4. 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
.\" @(#)sccs.1 2.10 (Berkeley) 7/24/91
helps them mesh more cleanly
also includes the capability to run
provide additional protection.
runs the command with the specified
Each argument is normally modified to be prepended with
Flags to be interpreted by the
program must be before the
Flags to be passed to the actual
program must come after the
These flags are specific to the command and
are discussed in the documentation for that command.
Perform a delta on the named files and
The new versions will have id keywords expanded, and
.\" anybody who has a bad xterm which is almost anyone
flags will be passed to get.
option is useful for making a
of your current editing phase. The same flags will be passed to delta
the initial contents from the file of the same name.
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 the
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
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.
is given, branches (i.e.,
with two or fewer components)
flag is given (with an optional argument) then
only files being edited by you (or the named user) are listed.
except that nothing is printed if nothing is being edited, and
a non-zero exit status is returned if anything is being edited.
The intent is to have this included in an
entry in a makefile to insure that everything is included into the
file before a version is installed.
Gives a newline-separated list of the files being edited
on the standard output. Takes the
listing between the current version of the
program(s) you have out for editing and the versions in
This command prints out verbose information
as the real user rather than as whatever effective user
Specifies a root directory for the
The default is the current directory.
it will be used to determine the
Defines the pathname of the directory in which the
argument is prepended to the entire pathname and the
argument is inserted before the final component of the pathname.
.Dq Li sccs \-d/x \-py get a/b
The intent here is to create aliases such as
.Dq Li alias syssccs sccs -d/usr/src
.Dq Li syssccs get cmd/who.c .
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:
.Dl sccs \-p/usr/src/sccs/s. get cc.c
.Dl 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:
.Dl sccs delta \`sccs tell \-u\`
In a makefile, to get source files
file if it does not already exist:
.Dl SRCS = <list of source files>
.Dl \&\tsccs get $(REL) $@
The PROJECT environment variable is checked by the
it begins with a slash, it is taken directly; otherwise,
the home directory of a user of that name is
examined for a subdirectory
If such a directory is found, it is used.
.%T "An Introduction to the Source Code Control System"
It should be able to take directory arguments on pseudo-commands