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

SCCS: Source Code Control System XENIX Programming
Including and Excluding Deltas
You can explicitly define which deltas you wish to include and which you wish to exclude
when creating a g-file by using the -i and -x options of the get command.
The -i option causes the command to apply the given deltas when constructing a version.
The -x option causes the command to ignore the given deltas when constructing a
version. Both options must be followed by one or more SIDs. If multiple SIDs are given,
they must be separated by commas (,). A range of SIDs may be given by separating two
SIDs with a hyphen (-). For example, the command
get -i 1.2, 1.3 s.demo.c
causes deltas 1.2 and 1.3 to be used to construct the g-file. The command
get -x1.2-1.4 s.demo.c
causes deltas 1.2 through 1.4 to be ignored when constructing the file.
The -i option is useful if you wish to apply the same changes to more than one version.
For example, the command
get -e -i4. 1 -r3.3 s.demo.c
retrieves version 3.3 for editing. When the file is retrieved, the changes in delta 4.1 are
automatically applied to it, making the g-file the same as if version 3.3 had been edited
by hand using the changes in delta 4.1. These changes can be saved immediately by
issuing a delta command. No editing is required.
The -x option is useful if you wish to remove changes performed on a given version. For
example, the command
get -e -x 1.5 -r1.6 s.demo.c
retrieves version 1.6 for editing. When the file is retrieved, the changes in delta 1.5 are
automatically left out of it, making the g-file the same as if version 1.4 had been
changed according to delta 1.6 (with no intervening delta 1.5). These changes can be
saved immediately by issuing a delta command. No editing is required.
When deltas are included or excluded, get compares them with the deltas normally used
in constructing the given version. If two deltas attempt to change the same line of the
retrieved file, the command displays a warning message. The message shows the range
of lines in which the problem may exist. Corrective action, if required, is the
responsibility of the user.
5-28