UNGET(1) General Commands Manual UNGET(1)

unget — undo a previous get of an SCCS file (DEVELOPMENT)

unget [-ns][-r SID] file...

The unget utility reverses the effect of a get(1) -e done prior to creating the intended new delta.

The unget utility supports the XBD specification, . The following options are supported:

Uniquely identify which delta is no longer intended. (This would have been specified by get(1) as the new delta.) The use of this option is necessary only if two or more outstanding get(1) commands for editing on the same SCCS file were done by the same person (login name).
Suppress the writing to standard output of the intended delta's SID.
Retain the file that was obtained by get(1) , which would normally be removed from the current directory.

The following operands are supported:

file
A pathname of an existing SCCS file or a directory. If file is a directory, unget behaves as though each file in the directory were specified as a named file, except that non-SCCS files (last component of the pathname does not begin with s.) and unreadable files are silently ignored. If a single instance file is specified as -, the standard input is read; each line of the standard input is taken to be the name of an SCCS file to be processed. Non-SCCS files and unreadable files are silently ignored.

The standard input is a text file used only when the file operand is specified as -. Each line of the text file is interpreted as an SCCS pathname.

Any SCCS files processed are files of an unspecified format.

The following environment variables affect the execution of unget :

Provide a default value for the internationalisation variables that are unset or null. If LANG is unset or null, the corresponding value from the implementation-dependent default locale will be used. If any of the internationalisation variables contains an invalid setting, the utility will behave as if none of the variables had been defined.
If set to a non-empty string value, override the values of all the other internationalisation variables.
Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single- as opposed to multi-byte characters in arguments and input files).
Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
Determine the location of message catalogues for the processing of LC_MESSAGES .

Default.

The standard output consists of a line for each file, in the following format:

"%s\n", <SID removed from file>

If there is more than one named file or if a directory or standard input is named, each pathname is written before each of the preceding lines:

"\n%s:\n", <pathname>

Used only for diagnostic messages.

Any SCCS files updated are files of an unspecified format. During processing of a file , a locking z@file , as described in get(1) , and a q@file (a working copy of the p@file ), may be created and deleted. The p@file and g@file , as described in get(1) , are deleted.

None.

The following exit values are returned:

Successful completion.
An error occurred.

Default.

None.

None.

None.

delta(1) , get(1) , sact(1) .

February 1997 posix.fail