delta - Saves editing changes in a Source Code Control System (SCCS) file
delta [-g list] [-m MRlist] [-n] [-p] [-s] [-r SID] [-y [comment]] file...|-
Interfaces documented on this reference page conform to industry standards as follows:
delta: XPG4, XPG4-UNIX
Refer to the
reference page for more information
about industry standards and associated tags.
Specifies a list of SIDs (deltas) that are to be ignored when the get command creates the g-file. After you use this option, get ignores the deltas in this list when it builds the g-file. Specifies a Modification Request (MR) number as the reason for creating the new delta.
The path name of an existing SCCS file or directory.
The delta command reads the g-files that correspond to the specified files (see the get(1) reference page) and creates a new delta.
The delta command introduces into the named SCCS file any changes that were made to the file version retrieved by an SCCS get -e command.
[Compaq] Avoid a get of many SCCS files followed by a delta of those files when the get generates a large amount of data. Instead, alternate the use of get and delta.
To use the delta command, do the following: Use get -e to get an editable version of the file. Edit that file. Use delta to create a new version of the SCCS file.
[Compaq] The delta command prompts you for comments. The comments are for that particular delta and appear in the SCCS file header. The comments are not retrieved when you get the delta and do not appear in the text of a retrieved file. Use comments to keep track of why a delta was created.
[Compaq] To see the comments, use an editor to look at the SCCS file, write the SCCS file to the display screen with the cat command, or print selected parts of the file to standard output using the prs command. Remember not to change the contents of the SCCS file directly. To change the delta comments, use the cdc(1) command.
[Compaq] SCCS does not allow use of the delta command if an editable file does not exist. However, once an editable file exists (created with get -e), SCCS creates the delta without checking the data being stored in the file.
Do not use the delta command on a file if it contains expanded identification keywords. Read-only file versions replace keywords with text values. Using delta on a read-only file causes the keywords to be lost. If this happens, remove the delta with the rmdel command or reedit the file and replace the identification keywords. SCCS does not allow you to use delta unless an editable copy of the file exists.
To prevent the loss of keywords, use the
option to specify the
Lines beginning with an
ASCII character (binary
001) cannot be placed in the SCCS file unless the
is quoted using a
has special meaning to SCCS and causes an error. See the
The following exit values are returned:
An error occurred.
To record changes you have made to an SCCS file, enter: delta s.prog.c
The following environment variables affect the execution of
Provides a default value for the internationalization variables
that are unset or null. If
is unset or null, the corresponding value from the default locale is used.
If any of the internationalization variables contain an invalid setting, the
utility behaves as if none of the variables had been defined.
If set to a non-empty string value, overrides the values of
all the other internationalization variables.
Determines the locale for the interpretation of sequences
of bytes of text data as characters (for example, single-byte as opposed to
multibyte characters in arguments and input files).
Determines the locale for the format and contents of diagnostic
messages written to standard error.
Determines the location of message catalogues for the processing
Commands: admin(1), bdiff(1), cdc(1), comb(1), get(1), prs(1), rmdel(1), sact(1), sccs(1), sccsdiff(1), sccshelp(1), unget(1), val(1), what(1)
Programming Support Tools