get.1

来自「<B>Digital的Unix操作系统VAX 4.2源码</B>」· 1 代码 · 共 755 行 · 第 1/2 页

Thus, for example, R.mL means the maximum
level number within release R;
R.L.(mB+1).1 means
the first sequence number on the
new branch (that is, maximum branch number plus
one) of level L within release R.
Note that if the \s-1SID\s+1 specified is of the form R.L,
R.L.B, or R.L.B.S, each of the
specified components must exist.
.TP
**
hR is the highest
existing release that is lower than
the specified, nonexistent, release\ R.
.TP
***
This is used to force creation of the
first delta in a new release.
.TP
#
Successor.
.TP
\(dg
The
.B \-b
option is effective only if the
.B b
flag 
is present in the file.
An entry of \fB\-\fR means ``irrelevant''.
For further information, see 
.MS admin 1 .
.TP
\(dd
This case applies if the
.B d
(default SID) flag is not present in the file.  If the
.B d
flag is present in the file, then the
SID obtained from the
.B d
flag is interpreted as if it had been specified on the command line.
Thus, one of the other cases in this table applies.
.SH Identification Keywords
.NXR "get command (sccs)" "identification keywords"
Identifying information
is inserted into the text retrieved from the \*(S) file by replacing
identification keywords
with their value wherever they occur.
The following keywords may be used in the text stored in an \*(S) file:
.TP 10
.I Keyword
.TP
.B %\&M\&%
Module name:
either the value of the
.B m
flag in the file
or if absent,
the name of the \*(S) file with the
leading
.B s.
removed.
For further information, see 
.MS admin 1 .
.TP
.B %\&I\&%
\*(S) identification (\*(I)) (%\&R\&%.%\&L\&%.%\&B\&%.%\&S\&%) of the retrieved text.
.TP
.B %\&R\&%
Release.
.TP
.B %\&L\&%
Level.
.TP
.B %\&B\&%
Branch.
.TP
.B %\&S\&%
Sequence.
.TP
.B %\&D\&%
Current date (\s-1YY/MM/DD\s+1).
.TP
.B %\&H\&%
Current date (\s-1MM/DD/YY\s+1).
.TP
.B %\&T\&%
Current time (\s-1HH:MM:SS\s+1).
.TP
.B %\&E\&%
Date newest applied delta was created (\s-1YY/MM/DD\s+1).
.TP
.B %\&G\&%
Date newest applied delta was created (\s-1MM/DD/YY\s+1).
.TP
.B %\&U\&%
The time the newest applied delta was created (\s-1HH:MM:SS\s+1).
.TP
.B %\&Y\&%
Module type:
value of the
.B t
flag in the \*(S) file
For further information, see 
.MS admin 1 .
.TP
.B %\&F\&%
\*(S) file name.
.TP
.B %\&P\&%
Fully qualified \*(S) file name.
.TP
.B %\&Q\&%
The
value of the
.B q
flag in the file.
For further information, see 
.MS admin 1 .
.TP
.B %\&C\&%
Current line number.
This keyword is intended for identifying output program messages
such as ``this shouldn't have happened'' type errors.
It is not intended to be used on every line to provide
sequence numbers.
.TP
.B %\&Z\&%
The 4-character string \fB@(#)\fR
recognizable by
.MS what 1 .
.TP
.B %\&W\&%
A shorthand notation for constructing
.MS what 1
strings
for \s-1UNIX\s+1 program files.
%\&W\&%~=~%\&Z\&%%\&M\&%<horizontal-tab>%\&I\&%
.TP
.B %\&A\&%
Another shorthand notation for constructing
.MS what 1
strings
for non-\s-1UNIX\s+1 program files.
%\&A\&%~=~%\&Z\&%%\&Y\&%~%\&M\&%~%\&I\&%%\&Z\&%
.SH Restrictions
.NXR "get command (sccs)" "restricted"
If the user has
write permission in the directory
containing the 
.I g-files,
but the real user does not,
then only one file can be named when the
.B \-e
option is used.
.SH Diagnostics
See
.MS sccshelp 1 
for explanations.
.SH Files
.NXR "get command (sccs)" "auxiliary file list"
Several auxiliary files may be created by
.PN get ,
These files are known generically as the
\fIg-file, l-file, p-file,\fR
and
\fIz-file\fR.
The letter before the hyphen is called the tag.
An auxiliary file name is formed from the \*(S) file name:
the last component of
all \*(S) file names must be of the form \fBs.\fP\fImodule-name\fP,
the auxiliary files are named by replacing the leading \fBs\fR
with the tag.
The
.I g-file
is an exception to this scheme:
the
.I g-file
is named by removing
the
.B s.
prefix.
For example,
.BR s.xyz.c ,
the auxiliary file names would be
.BR xyz.c ,
.BR l.xyz.c ,
.BR p.xyz.c ,
and
.BR z.xyz.c ,
respectively.
.PP
The
\fIg-file\fR,
which contains the generated text,
is created
in the current directory
(unless the
.B \-p
option is used).
A
.I g-file
is created in all cases, whether or not any lines of text
were generated by the
.PN get .
It is owned by the real user.
If the
.B \-k
option is used or implied its mode is 644;
otherwise its mode is 444.
Only the real user need have
write permission in the current
directory.
.PP
The
.I l-file
contains
a table showing which deltas were applied
in generating the retrieved text.
The
.I l-file
is created
in the current directory
if the
.B \-l
option is used;
its mode is 444 and it is owned by the real user.
Only the real user need have
write permission in the
current directory.
.PP
Lines in the
.I l-file
have the following format:
.PP
.PD 0
.RS
.nr a 0 1
.af a a
.TP
\n+a.
A blank character if the delta was applied;
.br
\fB\(**\fR otherwise.
.TP
\n+a.
A blank character if the delta was applied or wasn't applied and ignored;
.br
\fB\(**\fR if the delta wasn't applied and wasn't ignored.
.TP
\n+a.
A code indicating a ``special'' reason
why the delta was or was not applied:
.RS 10
\'I': Included.
.br
\'X': Excluded.
.br
\'C': Cut off (by a
.B \-c
option).
.RE
.TP
\n+a.
Blank.
.TP
\n+a.
\*(S) identification (\*(I)).
.TP
\n+a.
Tab character.
.TP
\n+a.
Date and time (in the form
\s-1YY/MM/DD~HH:MM:SS\s+1)
of creation.
.TP
\n+a.
Blank.
.TP
\n+a.
Login name of person who created delta.
.PD
.RE
.IP
The
comments and \*(M) data follow on subsequent lines,
indented one horizontal tab character.
A blank line terminates each entry.
.PP
The
.I p-file
is used to
pass information resulting from a
.PN get
with an
.B \-e
option along to
delta.
Its contents are also used to prevent a subsequent
execution of
.PN get
with an
.B \-e
option
for the same \*(I) until delta
is executed or the joint edit flag,
.BR j ,
see
.MS admin 1 ,
is set in the \*(S) file.
.PP
The
.I p-file
is created in the directory containing the \*(S) file
and the effective user must have
write permission
in that directory.
Its mode is 644 and it is owned by the effective user.
.PP
The format of the
.I p-file
is the following:
the gotten \*(I),
followed by a blank,
followed by the \*(I) that the new delta will have when it is made,
followed by a blank,
followed by the login name of the real user,
followed by a blank,
followed by the date-time
the
.PN get
was executed,
followed by a blank and the
.B \-i
option if it was present,
followed by a blank and the
.B \-x
option if it was present,
followed by a new-line.
There can be an arbitrary number of lines in the
.I p-file
at any time;
no two lines can have the same new delta \*(I).
.PP
The
.I z-file
serves as a
.I lock-out
mechanism against simultaneous updates.
Its contents are
the binary (two bytes) process \s-1ID\s+1 of the
command
.PN get
that created it.
The
.I z-file
is created in the directory containing the \*(S) file for the duration of 
.PN get .
The same protection restrictions for the
.I p-file
apply for the
\fIz-file\fR.
The
.I z-file
is
created mode 444.
.tr ~~
.SH See Also
admin(1), delta(1), prs(1), sccs(1), sccsfile(5), sccshelp(1),
what(1)
.br
\fIGuide to the Source Code Control System\fP
.NXE "get command (sccs)"
.NXE "SCCS file" "getting"