get(1) get(1)NAME get - gets a version of an SCCS file SYNOPSIS get [-aseq-no] [-b] [-ccutoff] [-e] [-g] [-ilist] [-k] [-l[p]] [-m] [-n] [-p] [-rSID] [-s] [-t] [-wstring] [-xlist] file... ARGUMENTS -aseq-no The delta sequence number of the SCCS file delta (version) to be retrieved (see sccsfile(4)). This keyletter is used by the comb(1) command; it is not a generally useful keyletter, and users should not use it. If both the -r and -a options are specified, the -a options is used. Care should be taken when using the -a option in conjunction with the -e option, as the SID of the delta to be created may not be what one expects. The -r option can be used with the -a and -e options to control the naming of the SID of the delta to be created. -b Indicates that the new delta should have an SID in a new branch as shown in Table 1, when used with the -e option. This option is ignored if the b is not present in the file (see admin(1)) or if the retrieved delta is not a leaf delta. (A leaf delta is one that has no successors on the SCCS file tree.) Note: A branch delta may always be created from a nonleaf delta. -ccutoff Specifies the cutoff date-time, in the form: YY[MM[DD[ HH[MM[SS]]]]]. No changes (deltas) to the SCCS file which were created after the specified cutoff date-time are included in the generated ASCII text file. Units omitted from the date-time default to their maximum possible values; that is, -c7502 is equivalent to -c750228235959. Any number of non-numeric characters may separate the various 2-digit pieces of the cutoff date-time. This feature allows one to specify a cutoff date in the form: -c77/2/2 9:22:25. Note that this implies that one may use the %E% and %U% identification keywords (see later) for a nested get within, for example, the input to a send(2N) command: ~!get "-c%E% %U%" s.file -e Indicates that the get is for the purpose of editing or January 1992 1
get(1) get(1)making a change (delta) to the SCCS file via a subsequent use of delta(1). When this option is used in a get command for a particular version (SID) of the SCCS file, it prevents a further get from editing on the same SID until delta is executed or the j (joint edit) flag is set in the SCCS file (see admin(1)). Concurrent use of get -e for different SIDs is always allowed. If the g-file generated by get with an -e option is accidentally ruined in the process of editing it, it may be regenerated by re-executing the get command with the -k option in place of the -e option. SCCS file protection specified via the ceiling, floor, and authorized user list stored in the SCCS file (see admin(1)) are enforced when the -e keyletter is used. file Specifies the file to be processed. -g Suppresses the actual retrieval of text from the SCCS file. It is primarily used to generate an l-file, or to verify the existence of a particular SID. -ilist Specifies a list of deltas to be included (forced to be applied) in the creation of the generated file. The list has the following syntax: <list> ::= <range> | <list> , <range> <range> ::= SID | SID-SID SID, the SCCS Identification of a delta, may be in any form shown in the ``SID Specified'' column; partial SIDs are interpreted as shown in the ``SID Retrieved'' column of Table 1. -k Suppresses the replacement of identification keywords (described below) in the retrieved text by their value. The -k option is implied by the -e option. -l[p] Causes a delta summary to be written into an l-file. If -lp is used, then an l-file is not created; the delta summary is written on the standard output instead. See NOTES for the format of the l-file. -m Causes each text line retrieved from the SCCS file to be preceded by the SID of the delta that inserted the text line in the SCCS file. The format is: SID, followed by a horizontal tab, followed by the text line. 2 January 1992
get(1) get(1)-n Causes each generated text line to be preceded with the %M% identification keyword value (described later) The format is: %M% value, followed by a horizontal tab, followed by the text line. When both the -m and -n options are used, the format is: %M% value, followed by a horizontal tab, followed by the -m option generated format. -p Causes the text retrieved from the SCCS file to be written on the standard output. No g-file is created. All output which normally goes to the standard output goes to file descriptor 2 instead, unless the -s option is used, in which case it disappears. -rSID Specifies the SCCS identification string (SID) of the version (delta) of an SCCS file to be retrieved. The table that follows these descriptions shows, for the most useful cases, what version of an SCCS file is retrieved (as well as the SID of the version to be eventually created by delta(1) if the -e keyletter is also used) as a function of the SID specified. -s Suppresses all output normally written on the standard output. However, fatal error messages (which always go to file descriptor 2) remain unaffected. -t Accesses the most recently created (top) delta in a given release (for example, -r1), or release and level (for example, -r1.2). -wstring Substitutes string for all occurrences of %W% when running get on the file. -xlist Specifies a list of deltas to be excluded (forced not to be applied) in the creation of the generated file. See the -i option for the list format. DESCRIPTION get generates an ASCII text file from each named SCCS file according to the specifications given by keyletter arguments that begin with -. The arguments may be specified in any order, but all keyletter arguments apply to all named SCCS files. If a directory is named, get behaves as though each file in the directory is 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 name of - is given, the standard input is read; each line of the standard input is taken to be the name of an SCCS file to be processed. Again, non-SCCS files and January 1992 3
get(1) get(1)unreadable files are silently ignored. The generated text is normally written into a file called the g-file, the name of which is derived from the SCCS filename simply by removing the leading s. (see also NOTES, later in this section). For each file processed, get responds (on the standard output) with the SID being accessed and with the number of lines retrieved from the SCCS file. If the -e options is used, the SID of the delta to be made appears after the SID accessed and before the number of lines generated. If there is more than one named file or if a directory or standard input is named, each filename is printed (preceded by a newline) before it is processed. If the -i option is used included deltas are listed following the notation Included; if the -x option is used, excluded deltas are listed following the notation Excluded. Determination of SCCS Identification String_________________________________________________________________SID* -b Keyletter Other SID SID of DeltaSpecified Used† Conditions Retrieved to be Created_________________________________________________________________none‡ no R defaults to mR mR.mL mR.(mL+1)_________________________________________________________________none‡ yes R defaults to mR mR.mL mR.mL.(mB+1).1_________________________________________________________________R no R > mR mR.mL R.1***_________________________________________________________________R no R = mR mR.mL mR.(mL+1)_________________________________________________________________R yes R > mR mR.mL mR.mL.(mB+1).1_________________________________________________________________R yes R = mR mR.mL mR.mL.(mB+1).1_________________________________________________________________R < mR andR - hR.mL** hR.mL.(mB+1).1R does not exist_________________________________________________________________Trunk succ.#R - in release > R R.mL R.mL.(mB+1).1and R exists_________________________________________________________________R.L no No trunk succ. R.L R.(L+1)_________________________________________________________________R.L yes No trunk succ. R.L R.L.(mB+1).1_________________________________________________________________Trunk succ.R.L - R.L R.L.(mB+1).1in release > R_________________________________________________________________R.L.B no No branch succ. R.L.B.mS R.L.B.(mS+1)_________________________________________________________________R.L.B yes No branch succ. R.L.B.mS R.L.(mB+1).1_________________________________________________________________R.L.B.S no No branch succ. R.L.B.S R.L.B.(S+1)_________________________________________________________________R.L.B.S yes No branch succ. R.L.B.S R.L.(mB+1).1 4 January 1992
get(1) get(1)_________________________________________________________________R.L.B.S - Branch succ. R.L.B.S R.L.(mB+1).1_________________________________________________________________* 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 the maximum level number within release R; ``R.L.(mB+1).1'' means the first sequence number on the new branch (i.e., maximum branch number plus one) of level L within release R. 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. ** ``hR'' is the highest existing release that is lower than the specified, nonexistent, release R. *** This is used to force creation of the first delta in a new release. # Successor. † The -b option is effective only if the b flag (see admin(1)) is present in the file. An entry of - means ``irrelevant.'' ‡ 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. Identification keywords 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: Keyword Value %M% Module name: either the value of the m flag in the file (see admin(1)), or if absent, the name of the SCCS file with the leading s. removed. %I% SCCS identification (SID) (%R%.%L%.%B%.%S%) of the retrieved text. %R% Release. %L% Level. %B% Branch. %S% Sequence. %D% Current date (YY/MM/DD). %H% Current date (MM/DD/YY). January 1992 5
get(1) get(1)%T% Current time (HH:MM:SS). %E% Date newest applied delta was created (YY/MM/DD). %G% Date newest applied delta was created (MM/DD/YY). %U% Time newest applied delta was created (HH:MM:SS). %Y% Module type: value of the t flag in the SCCS file (see admin(1)). %F% SCCS filename. %P% Fully qualified SCCS filename. %Q% The value of the q flag in the file (see admin(1)). %C% Current line number. This keyword is intended for identifying messages output by the program such as this should not have happened type errors. It is not intended to be used on every line to provide sequence numbers. %Z% The 4-character string @(#) recognizable by what(1). %W% A shorthand notation for constructing what(1) strings for A/UX system program files. %W%=%Z%%M%<horizontal-tab>%I% %A% Another shorthand notation for constructing what(1) strings for non-A/UX system program files. %A%=%Z%%Y%%M%%I%%Z% EXAMPLES The command: get -e s.file1 generates from the SCCS format file, s.file1, the text file, file1, for editing. NOTES Several auxiliary files may be created by get. These files are known generically as the g-file, l-file, p-file, and z-file. The letter before the hyphen is called the tag. An auxiliary filename is formed from the SCCS filename; the last component of all SCCS filenames must be of the form s.module-name, and the auxiliary files are named by replacing the leading s with the tag. The g-file is an exception to this scheme: the g-file is named by removing the s. prefix. For example, s.xyz.c, the auxiliary filenames would be xyz.c, l.xyz.c, p.xyz.c, and z.xyz.c, 6 January 1992
get(1) get(1)respectively. The g-file, which contains the generated text, is created in the current directory (unless the -p option is used). A g-file is created in all cases, whether or not any lines of text were generated by the get. It is owned by the real user. If the -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. The l-file contains a table showing which deltas were applied in generating the retrieved text. The l-file is created in the current directory if the -l keyletter 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. Lines in the l-file have the following format: a. A blank character if the delta was applied; * otherwise. b. A blank character if the delta was applied or was not applied and ignored; * if the delta was not applied and was not ignored. c. A code indicating a ``special reason'' why the delta was or was not applied: I: Included. X: Excluded. C: Cut off (by a -c option). d. Blank. e. SCCS identification (SID). f. TAB character. g. Date and time (in the form YY/MM/DD HH:MM:SS) of creation. h. Blank. i. Login name of person who created delta. The comments and MR data follow on subsequent lines, indented one horizontal tab character. A blank line terminates each entry. January 1992 7
get(1) get(1)The p-file is used to pass information resulting from a get with an -e option along to delta. Its contents are also used to prevent a subsequent execution of get with an -e option for the same SID until delta is executed or the joint edit flag, j, (see admin(1)) is set in the SCCS file. The p-file is created in the directory containing the SCCS file and the effective user must have write permission in that directory. Its mode is 644 and it is owned by the effective user. The format of the p-file is: the acquired SID, followed by a blank, followed by the SID 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 get was executed, followed by a blank and the -i option argument if it was present, followed by a blank and the -x option argument if it was present, followed by a newline. There can be an arbitrary number of lines in the p-file at any time; no two lines can have the same new delta SID. The z-file serves as a lock-out mechanism against simultaneous updates. Its contents are the binary (2 bytes) process ID of the command (that is, get) that created it. The z-file is created in the directory containing the SCCS file for the duration of get. The same protection restrictions as those for the p-file apply for the z-file. The z-file is created mode 444. LIMITATIONS If the effective user has write permission (either explicitly or implicitly) in the directory containing the SCCS files, but the real user does not, then only one file may be named when the -e option is used. DIAGNOSTICS Use help for explanations. FILES /usr/bin/get Executable file SEE ALSO admin(1), cdc(1), comb(1), delta(1), help(1), prs(1), rmdel(1), sact(1), sccs(1), sccsdiff(1), unget(1), val(1), what(1) sccsfile(4) in A/UX Programmer's Reference ``SCCS Reference'' in A/UX Programming Languages and Tools, Volume 2 8 January 1992