unget(1p)

1UNGET(1P)                  POSIX Programmer's Manual                 UNGET(1P)
2
3
4

PROLOG

6       This  manual  page is part of the POSIX Programmer's Manual.  The Linux
7       implementation of this interface may differ (consult the  corresponding
8       Linux  manual page for details of Linux behavior), or the interface may
9       not be implemented on Linux.
10

NAME

12       unget - undo a previous get of an SCCS file (DEVELOPMENT)
13

SYNOPSIS

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

DESCRIPTION

18       The unget utility shall reverse the effect of a get -e  done  prior  to
19       creating the intended new delta.
20

OPTIONS

22       The  unget  utility  shall  conform  to  the Base Definitions volume of
23       IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines.
24
25       The following options shall be supported:
26
27       -r  SID
28              Uniquely identify which delta is no longer intended. (This would
29              have  been  specified  by get as the new delta.) The use of this
30              option is necessary only if two or more outstanding get commands
31              for  editing  on the same SCCS file were done by the same person
32              (login name).
33
34       -s     Suppress the writing to standard output of the intended  delta's
35              SID.
36
37       -n     Retain  the  file that was obtained by get, which would normally
38              be removed from the current directory.
39
40

OPERANDS

42       The following operands shall be supported:
43
44       file   A pathname of an existing SCCS file or a directory. If file is a
45              directory, the unget utility shall behave as though each file in
46              the directory were specified as a named file, except  that  non-
47              SCCS  files  (last component of the pathname does not begin with
48              s.) and unreadable files shall be silently ignored.
49
50       If exactly one file operand appears, and it is '-', the standard  input
51       shall be read; each line of the standard input shall be taken to be the
52       name of an SCCS file to be processed.  Non-SCCS  files  and  unreadable
53       files shall be silently ignored.
54
55

STDIN

57       The standard input shall be a text file used only when the file operand
58       is specified as '-' . Each line of the text file shall  be  interpreted
59       as an SCCS pathname.
60

INPUT FILES

62       Any SCCS files processed shall be files of an unspecified format.
63

ENVIRONMENT VARIABLES

65       The  following  environment  variables  shall  affect  the execution of
66       unget:
67
68       LANG   Provide a default value for the  internationalization  variables
69              that  are  unset  or  null.  (See the Base Definitions volume of
70              IEEE Std 1003.1-2001, Section  8.2,  Internationalization  Vari‐
71              ables  for the precedence of internationalization variables used
72              to determine the values of locale categories.)
73
74       LC_ALL If set to a non-empty string value, override the values  of  all
75              the other internationalization variables.
76
77       LC_CTYPE
78              Determine  the  locale  for  the  interpretation of sequences of
79              bytes of text data as characters (for  example,  single-byte  as
80              opposed to multi-byte characters in arguments and input files).
81
82       LC_MESSAGES
83              Determine  the  locale  that should be used to affect the format
84              and contents of diagnostic messages written to standard error.
85
86       NLSPATH
87              Determine the location of message catalogs for the processing of
88              LC_MESSAGES .
89
90

ASYNCHRONOUS EVENTS

92       Default.
93

STDOUT

95       The  standard output shall consist of a line for each file, in the fol‐
96       lowing format:
97
98
99              "%s\n", <SID removed from file>
100
101       If there is more than one named file or  if  a  directory  or  standard
102       input  is named, each pathname shall be written before each of the pre‐
103       ceding lines:
104
105
106              "\n%s:\n", <pathname>
107

STDERR

109       The standard error shall be used only for diagnostic messages.
110

OUTPUT FILES

112       Any SCCS files updated shall be files of an unspecified format.  During
113       processing  of  a file, a locking z-file, as described in get, and a q-
114       file (a working copy of the p-file), may be created and deleted. The p-
115       file and g-file, as described in get, shall be deleted.
116

EXTENDED DESCRIPTION

118       None.
119

EXIT STATUS

121       The following exit values shall be returned:
122
123        0     Successful completion.
124
125       >0     An error occurred.
126
127

CONSEQUENCES OF ERRORS

129       Default.
130
131       The following sections are informative.
132

APPLICATION USAGE

134       None.
135

EXAMPLES

137       None.
138

RATIONALE

140       None.
141

FUTURE DIRECTIONS

143       None.
144

COPYRIGHT

149       Portions  of  this text are reprinted and reproduced in electronic form
150       from IEEE Std 1003.1, 2003 Edition, Standard for Information Technology
151       --  Portable  Operating  System  Interface (POSIX), The Open Group Base
152       Specifications Issue 6, Copyright (C) 2001-2003  by  the  Institute  of
153       Electrical  and  Electronics  Engineers, Inc and The Open Group. In the
154       event of any discrepancy between this version and the original IEEE and
155       The  Open Group Standard, the original IEEE and The Open Group Standard
156       is the referee document. The original Standard can be  obtained  online
157       at http://www.opengroup.org/unix/online.html .
158
159
160
161IEEE/The Open Group                  2003                            UNGET(1P)