sccs-unget(1)

📦 version 2022.10.16, in opensuse-leap 16.0

💅 sccs-unget(1) — like, the unget girlie of the SCCS fam

okay so bestie, welcome to sccs-unget (also known as plain *`unget``) — it's a *User Command, it's iconic, and it's literally here to undo your mistakes. we stan a supportive queen. 🫶

✨ NAME ✨

sccs-unget, unget — undoes a previous get of an SCCS file. it's the "nvm bestie, take it back" of version control. 😭

🌸 SYNOPSIS 🌸

/usr/ccs/bin/unget [-ns] [-q[nsedelim]] [-rsid]
    [-Nbulk-spec] s.filename...

💖 DESCRIPTION 💖

so the unget utility undoes the effect of a get -e command that was executed before the creation of the pending delta. it's giving "erase that, it never happened." ✨

if a directory name is used in place of the s.filename argument, the unget command applies to all s.files in that directory. (mass un-getting, we love efficiency 👑)

unreadable s.files produce an error, but processing keeps going with the next file (if any) — no quitter energy here, fr fr.

and using - as the s.filename argument means the names of files are to be read from standard input, one s.file per line. cute. 🎀

🦋 OPTIONS 🦋

the following options are supported:

  • -n — retains the retrieved version, which is otherwise removed. so like, keep the goods. 💅
  • -s — suppresses display of the SCCS delta ID (SID). quiet luxury. 🤫
  • -rsid — when multiple versions are checked out, this one specifies which pending delta to abort. you'll get a diagnostic if the specified SID is ambiguous, or if it's necessary but you omitted it from the command line. (so don't forget it, bestie, or it WILL call you out 😭)
  • -q[nsedelim] — enables NSE mode. if NSE mode is enabled, several NSE related extensions may be used. in this release, the value of nsedelim is ignored.
🚨 this option is an undocumented SUN extension that does not exist in historic sccs implementations. so it's giving "I'm not like other flags."
  • -Nbulk-spec — processes a bulk of SCCS history files. this option lets you do an efficient mass processing of SCCS history files. (group chat energy, but make it files. 🔥)

the bulk-spec parameter is composed from an optional list of flag parameters followed by an optional path specifier.

the following flag types are supported:

  • ++ — if bulk-spec is preceded by a ++, unget(1) expects to process filenames that are prepended by a plus sign, the related SID and another plus sign following the form:
+sid+filename

this permits each file to be retrieved with an individual SID. bespoke SIDs for everyone, we love to see it. 💜

  • space — this is a placeholder dummy flag that allows one to use a prepared string for the -N option and to replace the space character by one of the supported flags on demand. it's a stand-in, an understudy, a main character in waiting. 🎀

the following path specifier types are supported:

  • -N — the file name parameters to the unget command are not s.filename files but the names of the g-files. the s.filename names are automatically derived from the g-file names by prepending s. to the last path name component. both the s.filename and the g-file are in the same directory.
  • -Ns. — the file name parameters to the unget command are s.filename files. the g-files names are automatically derived by removing s. from the beginning of the last path name component of the s.filename. both the s.filename and the g-file are in the same directory.
  • -Ndir — the file name parameters to the unget command are not s.filename files but the names of the g-files. the s.filename names are put into directory dir; the names are automatically derived from the g-file names by prepending dir/s. to the last path name component.
  • -Ndir/s. — the file name parameters to the unget command are s.filename files in directory dir. the g-files names are automatically derived by removing dir/s. from the beginning of the last path name component of the s.filename.

a typical value for dir is SCCS. (iykyk 🌈)

in order to overcome the limited number of exec(2) arguments, it's recommended to use - as the file name parameter for unget(1) and to send a list of path names to stdin. strategy!! ⭐

🚨 this option is a SCHILY extension that does not exist in historic sccs implementations.
  • -Xextended-options — specify extended options. the argument extended-options may be a comma separated list of extended option names.

the following extended options are supported, they may be abbreviated as long as the abbreviation is still unique. options with parameter may not be abbreviated. (rules are rules 💅)

  • 0 — when reading filenames from stdin, triggered by a file name argument -, the filename separator is a null byte instead of a newline. this allows one to use long lists with arbitrary filenames. 🧚
  • help — prints a short online help for available options.
🚨 the -X option is a SCHILY extension that does not exist in historic sccs implementations.
  • -V, -version, --version — prints the unget version number string and exists. that's it, that's the whole job. 👑
🚨 this option is a SCHILY extension that does not exist in historic sccs implementations.

🐚 ENVIRONMENT VARIABLES 🐚

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

  • SCCS_NO_HELP — if set, unget(1) will not automatically call help(1) with the SCCS error code in order to print a more helpful error message. scripts that depend on the exact error messages of SCCS commands should set the environment variable SCCS_NO_HELP and set LC_ALL=C. yes, both. do not skip a step. 😤

🍓 EXIT STATUS 🍓

the following exit values are returned:

  • 0 — successful completion. slay. ✨
  • 1 — an error occurred. 💀

🎀 FILES 🎀

  • p.file — permissions (lock) file for checked-out versions. see sccs-get(1) for a description of the layout of the p.file.
  • q.file — temporary copy of the p.file; renamed to the p.file after completion.
  • z.file — temporary lock file contains the binary process id in host byte order followed by the host name.
  • dump.core — if the file dump.core exists in the current directory and a fatal signal is received, a coredump is initiated via abort(3). 😭 that's the drama we didn't ask for.

💜 ATTRIBUTES 💜

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

  • Attribute Type: Availability — Attribute Value: SUNWsprot
  • Attribute Type: Interface Stability — Attribute Value: Standard

🔥 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-val(1), bdiff(1), diff(1), what(1), sccschangeset(5), sccsfile(5), attributes(7), environ(7), standards(7).

(that's the whole group chat, bestie. everyone showed up. 👑)

🩺 DIAGNOSTICS 🩺

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

🙈 BUGS 🙈

None currently known. (we love a flawless era 💅✨)

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. (1972!! ancient icon behavior 🏛️)

Release 4.0 of SCCS — which introduced 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. legacies. 🫶

⬇️ 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

okay that's the whole page bestie!! go forth and un-get responsibly 💖

and hiii one last thing — this lil beauty is tagged SunOS 5.11, dated 2022/10/06, and it goes by sccs-unget(1) if you need to cite it in the group chat. mwah! 🎀🦋

📦 where this page comes from