unget(1)unget(1)NAMEunget - Cancels a previous get command
SYNOPSISunget [-n] [-s] [-r SID] file... | -
STANDARDS
Interfaces documented on this reference page conform to industry stan‐
dards as follows:
unget: XCU5.0
Refer to the standards(5) reference page for more information about
industry standards and associated tags.
OPTIONS
Each option or group of options applies independently to each named
file. Prevents the automatic deletion of the file obtained by get, the
g-file. This option lets you retain the edited version of the file
without making a delta. Specifies the new delta that would have been
created by the next use of the delta command. You must use this option
if you have two or more pending deltas to the file under the same login
name. You can look at the p-file to see if you have more than one
delta pending to a particular SID under the same login name. The SID
specification must unambiguously specify only one SID to discard, or
unget displays an error message and stops running. Suppresses display‐
ing the deleted SID.
OPERANDS
Pathname of an existing SCCS file or directory. If you specify a
directory unget performs the requested actions on all SCCS files (those
files with the s. prefix).
If you specify a - (dash) in place of file, standard input is
read, and each line of standard input is interpreted as the name
of a Source Code Control System (SCCS) file. An End-of-File
character terminates input.
DESCRIPTION
The unget command lets you restore a g-file created with a get -e
before the new delta is created, and therefore discard the changes (see
the get and delta commands).
The unget command lets you reverse the effect of a get -e command done
prior to creating the intended new delta.
[Tru64 UNIX] The file name or names refer to the SCCS s-files, not the
g-files. If the s-files are not in the working directory, the names
must include the path to the SCCS directory.
During processing of file, a locking z-file, and a q-file (a working
copy of the p-file), may be created and deleted. The p-file and g-file
are deleted. See get(1) for the descriptions and usage of these files.
EXIT STATUS
The following exit values are returned. Successful completion. An
error occurred.
EXAMPLES
To discard the changes you have made to an SCCS file after doing a get
-e, enter: unget s.prog.c The previous example illustrates use of unget
for an s-file in the working directory. The following example illus‐
trates use of the command for an s-file in a different directory: unget
/usr/projects/myproject/SCCS/s.prog.c
ENVIRONMENT VARIABLES
The following environment variables affect the execution of unget: Pro‐
vides a default value for the internationalization variables that are
unset or null. If LANG is unset or null, the corresponding value from
the implementation-specific default locale is used. If any of the
internationalization variables contain an invalid setting, unget
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 internation‐
alization variables. Determines the locale for the interpretation of
sequences of bytes of text data as characters (for example, single, as
opposed to multibyte, characters in arguments and input files). Deter‐
mines the locale that should be used to affect the format and contents
of diagnostic messages written to standard error. Determines the loca‐
tion of message catalogues for the processing of LC_MESSAGES.
SEE ALSO
Commands: admin(1), cdc(1), comb(1), delta(1), get(1), prs(1),
rmdel(1), sact(1), sccs(1), sccsdiff(1), sccshelp(1), val(1), what(1)
Files: sccsfile(4)
Standards: standards(5)
Programming Support Tools
unget(1)
