NAME¶

what - extract SCCS version information from a file

SYNOPSIS¶

what 
[-s] 
filename...

DESCRIPTION¶

The what utility searches each filename for occurrences of the pattern @(#) that the SCCS get command (see sccs-get(1)) substitutes for the %Z% ID keyword, and prints what follows up to a ", >, NEWLINE, \, or NULL character.

OPTIONS¶

The following option is supported:

-s

Stops after the first occurrence of the pattern.

-V

-version

--version

Prints the what version number string and exists.

This option is a SCHILY extension that does not exist in historic sccs implementations.

EXAMPLES¶

Example 1 Extracting SCCS version information

If a C program in file program.c contains

char sccsid[] = "@(#)identification information";

and program.c is compiled to yield program.o and a.out, the command:

example% 
what program.c program.o a.out

produces:

program.c:

identification information

program.o:

identification information

a.out:

identification information

ENVIRONMENT VARIABLES¶

See environ(7) for descriptions of the following environment variables that affect the execution of what: LANG, LC_ALL, LC_CTYPE, LC_MESSAGES, and NLSPATH.

EXIT STATUS¶

The following exit values are returned:

0

Any matches were found.

1

No matches found.

ATTRIBUTES¶

See attributes(7) for descriptions of the following attributes:

SEE ALSO¶

sccs(1), sccs-add(1), sccs-admin(1), sccs-branch(1), sccs-cdc(1), sccs-check(1), sccs-clean(1), sccs-comb(1), sccs-commit(1), sccs-create(1), sccs-cvt(1), sccs-deledit(1), sccs-delget(1), sccs-delta(1), sccs-diffs(1), sccs-edit(1), sccs-editor(1), sccs-enter(1), sccs-fix(1), sccs-get(1), sccs-help(1), sccs-histfile(1), sccs-info(1), sccs-init(1), sccs-istext(1), sccs-ldiffs(1), sccs-log(1), sccs-print(1), sccs-prs(1), sccs-prt(1), sccs-rcs2sccs(1), sccs-remove(1), sccs-rename(1), sccs-rmdel(1), sccs-root(1), sccs-sact(1), sccs-sccsdiff(1), sccs-status(1), sccs-tell(1), sccs-unedit(1), sccs-unget(1), sccs-val(1), sccschangeset(5), sccsfile(5), attributes(7), environ(7), standards(7).

DIAGNOSTICS¶

Use the SCCS help command for explanations (see sccs-help(1)).

BUGS¶

There is a remote possibility that a spurious occurrence of the `@(#)' pattern could be found by what.

Mail bugs and suggestions to schilytools@mlists.in-berlin.de or open a ticket at https://codeberg.org/schilytools/schilytools/issues.

The mailing list archive may be found at:

https://mlists.in-berlin.de/mailman/listinfo/schilytools-mlists.in-berlin.de.

AUTHORS¶

The SCCS suite was originally written by Marc J. Rochkind at Bell Labs in 1972. Release 4.0 of SCCS, introducing new versions of the programs admin(1), get(1), prt(1), and delta(1) was published on February 18, 1977; it introduced the new text based SCCS v4 history file format (previous SCCS releases used a binary history file format). The SCCS suite was later maintained by various people at AT&T and Sun Microsystems. Since 2006, the SCCS suite has been maintained by Joerg Schilling and the schilytools project authors.

SOURCE DOWNLOAD¶

The source code for sccs is included in the schilytools project and may be retrieved from the schilytools project at Codeberg at

https://codeberg.org/schilytools/schilytools.

The download directory is

https://codeberg.org/schilytools/schilytools/releases.