get.html

unix 下的C开发手册,还用详细的例程。

These files are known generically as the
<i>g-file</i>,
<i>l-file</i>,
<i>p-file</i>
and
<i>z-file</i>.
The letter before the hyphen is called the
<i>tag .</i>
An auxiliary filename is formed from the SCCS file name:
the last component of
all SCCS filenames must be of the form
s.<i>module-name</i>
the auxiliary files are named by replacing the leading
s
with the tag.
The
<i>g-file</i>
is an exception to this scheme:
the
<i>g-file</i>
is named by removing the
s.
prefix.
For example, for
<b>s.xyz.c</b>,
the auxiliary filenames would be
<b>xyz.c</b>,
<b>l.xyz.c</b>,
<b>p.xyz.c</b>
and
<b>z.xyz.c</b>,
respectively.
<p>
The
<i>g-file</i>,
which contains the generated text,
is created in the current directory (unless the
<b>-p</b>
option is used).
A
<i>g-file</i>
is created in all cases, whether or not any lines of text
were generated by the
<i>get</i>.
It is owned by the real user.
If the
<b>-k</b>
option is used or implied, it is writable by the
owner only (read-only for everyone else);
otherwise it is read-only.
Only the real user need have
write permission in the current directory.
<p>
The
<i>l-file</i>
contains a table showing which deltas were applied
in generating the retrieved text.
The
<i>l-file</i>
is created in the current directory if the
<b>-l</b>
option is used;
it is read-only and it is owned by the real user.
Only the real user need have write permission in the
current directory.
<p>
Lines in the
<i>l-file</i>
have the following format:
<code>
<p>
<tt>"%c%c%c<img src="../images/delta.gif" border=0>%s\t%s<img src="../images/delta.gif" border=0>%s\n"</tt>, &lt;<i>code1</i>&gt;,
&lt;<i>code2</i>&gt;,
&lt;<i>code3</i>&gt;,
&lt;<i>SID</i>&gt;,
&lt;<i>date-time</i>&gt;,
&lt;<i>login</i>&gt;
</code>
</p>
<p>
where the entries are:
<dl compact>

<dt>&lt;<i>code1</i>&gt;<dd>A space character if the delta was applied;
"*" otherwise.

<dt>&lt;<i>code2</i>&gt;<dd>A space character if the delta was applied or was not applied and ignored;
"*" if the delta was not applied and was not ignored.

<dt>&lt;<i>code3</i>&gt;<dd>A character indicating a special reason
why the delta
was or was not applied:
<dl compact>

<dt><b>I</b><dd>Included.

<dt><b>X</b><dd>Excluded.

<dt><b>C</b><dd>Cut off (by a
<b>-c</b>
option).

</dl>
<p>
<dt>&lt;<i>date-time</i>&gt;<dd>
Date and time (using the
<i><a href="date.html">date</a></i>
utility's
%y/%m/%d%T
format)
of creation.
<p>
<dt>&lt;<i>login</i>&gt;<dd>Login name of person who created
<i><a href="delta.html">delta</a></i>.
<p>
</dl>
<p>
The comments and MR data follow on subsequent lines,
indented one tab character.
A blank line terminates each entry.
<p>
The
<i>p-file</i>
is used to pass information resulting from a
<i>get</i>
with a
<b>-e</b>
option along to
<i><a href="delta.html">delta</a></i>.
Its contents are also used to prevent a subsequent execution of
<i>get</i>
with a
<b>-e</b>
option for the same SID until
<i><a href="delta.html">delta</a></i>
is executed or the joint edit flag,
j,
is set in the SCCS file.
The
<i>p-file</i>
is created in the directory containing the SCCS file
and the effective user must have write permission in that directory.
It is writable by owner only, and it is owned by the effective user.
Each line in the
<i>p-file</i>
has the following format:
<code>
<p>
<tt>"%s<img src="../images/delta.gif" border=0>%s<img src="../images/delta.gif" border=0>%s<img src="../images/delta.gif" border=0>%s%s%s\n"</tt>, &lt;<i>g-file&nbsp;SID</i>&gt;,
&lt;<i>SID&nbsp;of&nbsp;new&nbsp;delta</i>&gt;,
&lt;<i>login-name&nbsp;of&nbsp;real&nbsp;user</i>&gt;,
&lt;<i>date-time</i>&gt;,
&lt;<i>i-value</i>&gt;,
&lt;<i>x-value</i>&gt;
</p>
</code>
<p>
where
&lt;<i>i-value</i>&gt;
uses the format &quot;&quot; if no <b>-i</b> option
was specified and uses the format:
<code>
<p>
<tt>"<img src="../images/delta.gif" border=0>-i%s"</tt>, &lt;<i>i option option-argument</i>&gt;
</p>
</code>
if a <b>-i</b> option was specified, and 
&lt;<i>x-value</i>&gt;
uses the format &quot;&quot; if no <b>-x</b> option was specified,
and uses the format:
<code>
<p>
<tt>"<img src="../images/delta.gif" border=0>-x%s"</tt>, &lt;<i>x option option-argument</i>&gt;
</p>
</code>
if a <b>-x</b> option was specified. 
There can be an arbitrary number of lines in the
<i>p-file</i>
at any time; no two lines can have the same new delta SID.
<p>
The
<i>z-file</i>
serves as a lock-out mechanism against simultaneous updates.
Its contents are the binary process ID of the
command (that is,
<i>get</i>)
that created it.
The
<i>z-file</i>
is created in the directory containing the SCCS file for the duration of
<i>get</i>.
The same protection restrictions as those for the
<i>p-file</i>
apply for the
<i>z-file</i>.
The
<i>z-file</i>
is created read-only.
<br>
</blockquote><h4><a name = "tag_001_014_845">&nbsp;</a>EXTENDED DESCRIPTION</h4><blockquote>
<pre>
<table  bordercolor=#000000 border=1 align=center><tr valign=top><th colspan=5 align=center><b>Determination of SCCS Identification String</b>
<tr valign=top><th align=center><b>SID*</b>
<th align=center><b>-b Keyletter</b>
<th align=center><b>Other</b>
<th align=center><b>SID</b>
<th align=center><b>SID of Delta</b>
<tr valign=top><th align=center><b>Specified</b>
<th align=center><b>Used</b>
<th align=center><b>Conditions</b>
<th align=center><b>Retrieved</b>
<th align=center><b>to be Created</b>
<tr valign=top><td align=left>none
<td align=center>no
<td align=center>R defaults to mR
<td align=left>mR.mL
<td align=left>mR.(mL+1)
<tr valign=top><td align=left>none
<td align=center>yes
<td align=center>R defaults to mR
<td align=left>mR.mL
<td align=left>mR.mL.(mB+1).1
<tr valign=top><td align=left>R
<td align=center>no
<td align=center>R &gt; mR
<td align=left>mR.mL
<td align=left>R.1***
<tr valign=top><td align=left>R
<td align=center>no
<td align=center>R = mR
<td align=left>mR.mL
<td align=left>mR.(mL+1)
<tr valign=top><td align=left>R
<td align=center>yes
<td align=center>R &gt; mR
<td align=left>mR.mL
<td align=left>mR.mL.(mB+1).1
<tr valign=top><td align=left>R
<td align=center>yes
<td align=center>R = mR
<td align=left>mR.mL
<td align=left>mR.mL.(mB+1).1
<tr valign=top><td align=left>R
<td align=center>-
<td align=center> R &lt; mR and R does not exist 
<td align=left>hR.mL**
<td align=left>hR.mL.(mB+1).1
<tr valign=top><td align=left>R
<td align=center>-
<td align=center> Trunk successor in release &gt; R and R exists 
<td align=left>R.mL
<td align=left>R.mL.(mB+1).1
<tr valign=top><td align=left>R.L
<td align=center>no
<td align=center>No trunk successor
<td align=left>R.L
<td align=left>R.(L+1)
<tr valign=top><td align=left>R.L
<td align=center>yes
<td align=center>No trunk successor
<td align=left>R.L
<td align=left>R.L.(mB+1).1
<tr valign=top><td align=left>R.L
<td align=center>-
<td align=center> Trunk successor in release &gt;= R 
<td align=left>R.L
<td align=left>R.L.(mB+1).1
<tr valign=top><td align=left>R.L.B
<td align=center>no
<td align=center>No branch successor
<td align=left>R.L.B.mS
<td align=left>R.L.B.(mS+1)
<tr valign=top><td align=left>R.L.B
<td align=center>yes
<td align=center>No branch successor
<td align=left>R.L.B.mS
<td align=left>R.L.(mB+1).1
<tr valign=top><td align=left>R.L.B.S
<td align=center>no
<td align=center>No branch successor
<td align=left>R.L.B.S
<td align=left>R.L.B.(S+1)
<tr valign=top><td align=left>R.L.B.S
<td align=center>yes
<td align=center>No branch successor
<td align=left>R.L.B.S
<td align=left>R.L.(mB+1).1
<tr valign=top><td align=left>R.L.B.S
<td align=center>-
<td align=center>Branch successor
<td align=left>R.L.B.S
<td align=left>R.L.(mB+1).1
</table>
</pre>
<dl compact>

<dt>*<dd>R, L, B and S are the release, level,
branch and sequence components of the SID, respectively;
m means maximum.
Thus, for example,
R.mL means &quot;the maximum level number within release R&quot;;
R.L.(mB+1).1 means &quot;the first sequence number on the
new branch (that is, maximum branch number plus
one) of level L within release R&quot;.
Note that if the SID specified is of the form R.L,
R.L.B or R.L.B.S, each of the specified components must exist.

<dt>**<dd>hR is the highest existing release that is lower than
the specified, non-existent, release R.

<dt>***<dd>This is used to force creation of the first
delta in a new release.

<dt><dd>The
<b>-b</b>
option is effective only if the
b
flag is present in the file.
An entry of - means &quot;irrelevant&quot;.


<dt><dd>This case applies if the
d
(default SID) flag is not present in the file.
If the
d
flag is present in the file, then the
SID obtained from the
d
flag is interpreted as if it had been specified on the command line.
Thus, one of the other cases in this table applies.

</dl>
<h5><a name = "tag_001_014_845_001">&nbsp;</a>Identification Keywords</h5>
Identifying information is inserted into the text retrieved from the
SCCS file by replacing identification keywords with their value
wherever they occur.
The following keywords may be used in the text stored in an SCCS file:
<dl compact>

<dt><b>%M%</b><dd>Module name: either the value of the
m
flag in the file, or if absent,
the name of the SCCS file with the leading
s.
removed.

<dt><b>%I%</b><dd>SCCS identification (SID)
(<i>%R%.%L%</i>
or
<i>%R%.%L%.%B%.%S%</i>)
of the retrieved text

<dt><b>%R%</b><dd>Release.

<dt><b>%L%</b><dd>Level.

<dt><b>%B%</b><dd>Branch.

<dt><b>%S%</b><dd>Sequence.

<dt><b>%D%</b><dd>Current date (<i>YY</i>/<i>MM</i>/<i>DD</i>).

<dt><b>%H%</b><dd>Current date (<i>MM</i>/<i>DD</i>/<i>YY</i>).

<dt><b>%T%</b><dd>Current time (<i>HH</i>:<i>MM</i>:<i>SS</i>).

<dt><b>%E%</b><dd>Date newest applied delta was created (<i>YY</i>/<i>MM</i>/<i>DD</i>).

<dt><b>%G%</b><dd>Date newest applied delta was created (<i>MM</i>/<i>DD</i>/<i>YY</i>).

<dt><b>%U%</b><dd>Time newest applied delta was created (<i>HH</i>:<i>MM</i>:<i>SS</i>).

<dt><b>%Y%</b><dd>Module type: value of the
t
flag in the SCCS file.

<dt><b>%F%</b><dd>SCCS filename.

<dt><b>%P%</b><dd>SCCS absolute pathname.

<dt><b>%Q%</b><dd>The value of the
q
flag in the file.

<dt><b>%C%</b><dd>Current line number.
This keyword is intended for identifying messages output by the
program, such as &quot;this should not have happened&quot; type errors.
It is not intended to be used on every line to provide
sequence numbers.

<dt><b>%Z%</b><dd>The four-character string
@(#)
recognisable by
<i><a href="what.html">what</a></i>.

<dt><b>%W%</b><dd>A shorthand notation for constructing
<i><a href="what.html">what</a></i>
strings:
<pre>
<code>
%W%=%Z%%M%&lt;tab&gt;%I%
</code>
</pre>

<dt><b>%A%</b><dd>Another shorthand notation for constructing
<i><a href="what.html">what</a></i>
strings:
<pre>
<code>
%A%=%Z%%Y%%M%%I%%Z%
</code>
</pre>

</dl>
</blockquote><h4><a name = "tag_001_014_846">&nbsp;</a>EXIT STATUS</h4><blockquote>
The following exit values are returned:
<dl compact>

<dt>0<dd>Successful completion.

<dt>&gt;0<dd>An error occurred.

</dl>
</blockquote><h4><a name = "tag_001_014_847">&nbsp;</a>CONSEQUENCES OF ERRORS</h4><blockquote>
Default.
</blockquote><h4><a name = "tag_001_014_848">&nbsp;</a>APPLICATION USAGE</h4><blockquote>
None.
</blockquote><h4><a name = "tag_001_014_849">&nbsp;</a>EXAMPLES</h4><blockquote>
None.
</blockquote><h4><a name = "tag_001_014_850">&nbsp;</a>FUTURE DIRECTIONS</h4><blockquote>
The
<b>-lp</b>
option may be withdrawn in a future issue.
</blockquote><h4><a name = "tag_001_014_851">&nbsp;</a>SEE ALSO</h4><blockquote>
<i><a href="admin.html">admin</a></i>,
<i><a href="delta.html">delta</a></i>,
<i><a href="prs.html">prs</a></i>,
<i><a href="what.html">what</a></i>.
</blockquote><hr size=2 noshade>
<center><font size=2>
UNIX &reg; is a registered Trademark of The Open Group.<br>
Copyright &copy; 1997 The Open Group
<br> [ <a href="../index.html">Main Index</a> | <a href="../xshix.html">XSH</a> | <a href="../xcuix.html">XCU</a> | <a href="../xbdix.html">XBD</a> | <a href="../cursesix.html">XCURSES</a> | <a href="../xnsix.html">XNS</a> ]

</font></center><hr size=2 noshade>
</body></html>