Intel XENIX 286 Programmers Guide (86) - Tenox.tc

XENIX Programming SCCS: Source Code Control System
prints all information about versions that precede version 1.4 (e.g., 1.3, 1.2, and 1.1).
The command
prs -r1.4 -1 s.abc
prints information about versions that succeed version 1.4 (e.g., 1.5, 1.6, and 2.1).
If both options are given, information about all versions is printed.
Editing by Several Users
SCCS allows any nu mber of users to access and edit versions of a given s-file. Since
users are likely to access the s-file at the same time, the system is designed to allow
concurrent editing of different versions. Normally, the system prevents concurrent
editing of the same version, but you can change the operation of the system to allow
concurrent editing of the same version by setting the j flag in the given s-file.
The following sections explain how to perform concurrent editing and how to save edited
versions when you have retrieved more than one version for editing.
Editing Different Versions
sees allows several different versions of a file to be edited at the same time. This
means a user can edit version 2.1 while another user edits version 1.1. There is no limit
to the number of versions that can be edited at any given time.
When several users edit different versions concurrently, each user must begin work in
his own directory. If users attempt to share a directory and work on versions from the
same s-file at the same time, the get command will refuse to retrieve a version.
Editing a Single Version
A single version of a file can be edited by more than one user if the j flag is set in the sfile.
The flag causes the get command to check the p-file and create a new proposed
SID if the given version is already being edited.
You can set the flag by using the -f option of the admin command. For example, the
command
admin -fj s.demo.c
sets the flag for the s-file s.demo.c.
When the flag is set, get uses the next available branch SID for each new proposed SID.
For example, suppose a user retrieves for editing version 1.4 in the file s.demo.c and
that the proposed version is 1.5. If a short time later (before the first user has saved his
changes) another user retrieves version 1.4 for editing, then the proposed version for the
new user will be 1.4.1.1, since version 1.5 is already proposed and likely to be taken. In
no case will a version edited by two separate users result in a single new version.
5-21