sccs-clean(1)

πŸ“¦ version 2022.10.16, in opensuse-leap 16.0

πŸ’… sccs-clean(1) β€” SchilyΒ΄s USER COMMANDS ✨

okay bestie, welcome to sccs-clean, a page from SchilyΒ΄s USER COMMANDS and literally the "start fresh" button of the SCCS world πŸ§ΉπŸ’–


πŸŽ€ NAME πŸŽ€

sccs-clean β€” removes literally everything from a directory that can be retrieved from SCCS history πŸ‘‘


✨ SYNOPSIS ✨

sccs clean [options] [subdirectory]

πŸ¦‹ DESCRIPTION πŸ¦‹

So the clean subcommand is the glow-up-your-directory subcommand: it removes everything from the current directory that can be recreated from SCCS history files. no cap. ✨

It will not remove any files that are being edited β€” those are safe, periodt πŸ’…

If the -b flag is given, branches are ignored in the determination of whether they are being edited. and like, this is dangerous if you are keeping the branches in the same directory πŸ™ˆ keep that in mind fr fr.

If the subdirectory argument is omitted, '.' is assumed. cute and convenient πŸŽ€


πŸ’œ OPTIONS πŸ’œ

  • -b β€” do not check branches to see if they are being edited. clean -b is dangerous when branch versions are kept in the same directory πŸ’€ (yes, we said it twice, because it matters twice)

🌸 EXAMPLES 🌸

To create a new SCCS repository in the current directory call:

sccs clean .

🌈 ENVIRONMENT VARIABLES 🌈

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

  • SCCS_NO_HELP β€” if set, sccs clean 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. iykyk 😭

πŸ‘‘ ATTRIBUTES πŸ‘‘

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

  • Attribute Type: Availability β€” Attribute Value: SCHILYdeveloper-build-sccs ⭐
  • Attribute Type: Interface Stability β€” Attribute Value: Committed πŸ’–

πŸ“ SEE ALSO πŸ“

sccs(1), sccs-add(1), sccs-admin(1), sccs-branch(1), sccs-cdc(1), sccs-check(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), what(1), sccschangeset(5), sccsfile(5). the whole friend group honestly πŸ’œ


πŸ’€ BUGS πŸ’€

None currently known. iconic behaviour, honestly 🧚✨

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 πŸŽ€

sccs clean was originally written by Eric Allman at UCB in 1980. It was later maintained by various people at AT&T and Sun Microsystems. Since 2006, it has been maintained by Joerg Schilling and the schilytools project authors. a whole legacy, main character energy πŸ‘‘


πŸ”₯ 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 clean πŸ§ΉπŸ’–

✨ brought to you by Joerg Schilling, dated 2022/10/06 β€” that's the sccs-clean(1) energy, mwah πŸ’…πŸŒŸ
πŸ“¦ where this page comes from