unget (1p) - Linux Man Pages
unget: undo a previous get of an SCCS file (DEVELOPMENT)
PROLOGThis manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the corresponding Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux.
unget - undo a previous get of an SCCS file (DEVELOPMENT)
The unget utility shall conform to the Base Definitions volume of IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines.
The following options shall be supported:
- Uniquely identify which delta is no longer intended. (This would have been specified by get as the new delta.) The use of this option is necessary only if two or more outstanding get 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, which would normally
be removed from the
The following operands shall be supported:
- A pathname of an existing SCCS file or a directory. If file is a directory, the unget utility shall behave 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 shall be silently ignored.
If exactly one file operand appears, and it is '-', the standard input shall be read; each line of the standard input shall be taken to be the name of an SCCS file to be processed. Non-SCCS files and unreadable files shall be silently ignored.
The following environment variables shall affect the execution of unget:
- Provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of IEEE Std 1003.1-2001, Section 8.2, Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.)
- If set to a non-empty string value, override the values of all the other internationalization variables.
- Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte 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 catalogs for the processing of LC_MESSAGES
The standard output shall consist 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 shall be written before each of the preceding lines:
Any SCCS files updated shall be files of an unspecified format. During processing of a file, a locking z-file, as described in get, 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, shall be deleted.
The following exit values shall be returned:
- Successful completion.
- An error occurred.
CONSEQUENCES OF ERRORS
COPYRIGHTPortions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .