![]() |
![]()
| ![]() |
![]()
NAMEsccs-status - show changed files in the project SYNOPSISsccs status [options] [file1 .. filen] DESCRIPTIONThe status subcommand shows the status of the files in the repository. If no file argument is given, the current list of files in the project is checked. This subcommand is a project extension that does not exist in historic sccs implementations. EXAMPLESTo check for changed files in the current directory, call:
ENVIRONMENT VARIABLESSee environ(7) for descriptions of the following environment variables that affect the execution of sccs-status(1): LANG, LC_ALL, LC_CTYPE, LC_MESSAGES, and NLSPATH.
ATTRIBUTESSee attributes(7) for descriptions of the following attributes:
SEE ALSOsccs(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-tell(1), sccs-unedit(1), sccs-unget(1), sccs-val(1), what(1), sccschangeset(5), sccsfile(5). BUGSNone currently known. 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. AUTHORsccs status was originally written by Joerg Schilling in 2015 and is now maintained by the schilytools project authors. SOURCE DOWNLOADThe 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.
|