delta(1) DG/UX 4.30 delta(1)
NAME
delta - make a delta (change) to an SCCS file
SYNOPSIS
delta [-rSID] [-s] [-n] [-glist] [-m[mrlist]] [-y[comment]]
[-p] files
DESCRIPTION
Delta permanently introduces into the named SCCS file
changes that were made to the file retrieved by get(1)
(called the g-file, or generated file).
Delta adds a change to each named SCCS file. If a directory
is named, delta behaves as though each file in the directory
were specified as a named file, except that non-SCCS files
(last component of the path name does not begin with s.)
and unreadable files are ignored. If a name of - is given,
the standard input is read (see WARNINGS); each line of the
standard input is taken to be the name of an SCCS file to be
processed.
Delta may issue prompts on the standard output, depending on
options specified and flags (see admin(1)) that may be
present in the SCCS file (see -m and -y options below).
Options apply independently to each named file.
-rSID Uniquely identifies which delta is to be
made to the SCCS file. This option is
necessary only if two or more
outstanding gets for editing (get -e) on
the same SCCS file were done by the same
person (login name). The SID value
specified with the -r option can be
either the SID specified on the get
command line or the SID to be made as
reported by the get command (see
get(1)). A diagnostic results if the
specified SID is ambiguous, or, if
necessary and omitted on the command
line.
-s Suppresses the issue, on the standard
output, of the created delta's SID, as
well as the number of lines inserted,
deleted and unchanged in the SCCS file.
-n Retains the edited g-file (normally
removed at completion of delta
processing).
-glist Specifies a list (see get(1) for the
Licensed material--property of copyright holder(s) Page 1
delta(1) DG/UX 4.30 delta(1)
definition of list) of deltas to be
ignored when the file is accessed at the
change level (SID) created by this
delta.
-m[mrlist] If the SCCS file has the v flag set (see
admin(1)) then a Modification Request
(MR) number must be supplied as the
reason for creating the new delta.
If -m is not used and the standard input
is a terminal, the prompt MRs? is issued
on the standard output before the
standard input is read; if the standard
input is not a terminal, no prompt is
issued. The MRs? prompt always precedes
the comments? prompt (see -y option).
MRs in a list are separated by blanks and/or tab
characters. An unescaped new-line character terminates
the MR list.
Note that if the v flag has a value (see
admin(1)), it is taken to be the name of
a program (or shell procedure) that will
validate the MR numbers. If a non-zero
exit status is returned from the MR
number validation program, delta
terminates (assumes that the MR numbers
were not all valid).
-y[comment] Arbitrary text that describes the reason
for making the delta. A null string is
considered a valid comment.
If -y is not specified and the standard
input is a terminal, the prompt
comments? is issued on the standard
output before the standard input is
read; if the standard input is not a
terminal, no prompt is issued. An
unescaped new-line character terminates
the comment text.
-p Prints (on the standard output) the SCCS
file differences before and after the
delta is applied in a diff(1) format.
EXAMPLES
$ delta /work/archives/s.file1
Licensed material--property of copyright holder(s) Page 2
delta(1) DG/UX 4.30 delta(1)
This command permanently installs any changes done to
'file1' (the g-file), which must be in the current working
directory, into the SCCS file 's.file1' in the directory
/work/archives.
$ delta -ytest -n -p s.file2
This command permanently installs any changes done to
'file2' (the g-file) into the SCCS file 's.file2', including
adding the description found in 'test' as the reason for
making the change, as well as not removing the file 'file2'
from the current directory. The -p will list the before and
after differences of the SCCS file.
FILES
All files of the form ?-file are explained in Using DG/UX
System Programming Tools The naming convention for these
files is also described there.
g-file Existed before the execution of delta; removed
after completion of delta.
p-file Existed before the execution of delta; may
exist after completion of delta.
q-file Created during the execution of delta; removed
after completion of delta.
x-file Created during the execution of delta; renamed
to SCCS file after completion of delta.
z-file Created during the execution of delta; removed
during the execution of delta.
d-file Created during the execution of delta; removed
after completion of delta.
/bin/bdiff Program to compute differences between the
"gotten" file and the g-file.
WARNINGS
Lines beginning with an SOH ASCII character (binary 001)
cannot be placed in the SCCS file unless the SOH is escaped.
This character has special meaning to SCCS (see sccsfile(4)
(5)) and will cause an error.
A get of many SCCS files, followed by a delta of those
files, should be avoided when the get generates a large
amount of data. Instead, use multiple get/delta sequences.
If the standard input (-) is specified on the delta command
line, the -m (if necessary) and -y options must also be
present. Omission of these options causes an error to
occur.
Comments are limited to text strings of at most 512
characters.
Licensed material--property of copyright holder(s) Page 3
delta(1) DG/UX 4.30 delta(1)
SEE ALSO
admin(1), bdiff(1), cdc(1), comb(1), get(1), help(1),
prs(1), rmdel(1).
sccsfile(4) in the Programmer's Reference for the DG/UX
System (Volume 2)
"Source Code Control System" in Using DG/UX System
Programming Tools.
DIAGNOSTICS
Use help(1) for explanations.
Licensed material--property of copyright holder(s) Page 4