{ "content": [ { "type": "text", "text": "# CI (man)\n\n## NAME\n\nci - check in RCS revisions\n\n## SYNOPSIS\n\nci [options] file ...\n\n## DESCRIPTION\n\nci stores new revisions into RCS files. Each file name matching an RCS suffix is taken to be\nan RCS file. All others are assumed to be working files containing new revisions. ci de‐\nposits the contents of each working file into the corresponding RCS file. If only a working\nfile is given, ci tries to find the corresponding RCS file in an RCS subdirectory and then in\nthe working file's directory. For more details, see FILE NAMING below.\n\n## TLDR\n\n> Check in RCS revisions (store file changes in the Revision Control System).\n\n- Check in a file and keep the working file unlocked:\n `ci -u {{path/to/file}}`\n- Check in a file and keep the working file locked:\n `ci -l {{path/to/file}}`\n- Check in a file with a specific log message:\n `ci -m\"{{log_message}}\" {{path/to/file}}`\n- Check in a file, unlocking it but leaving the working file read-only:\n `ci {{path/to/file}}`\n- Force check-in even if there are no changes:\n `ci -f -u {{path/to/file}}`\n\n*Source: tldr-pages*\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION** (1 subsections)\n- **OPTIONS** (25 subsections)\n- **FILE NAMING**\n- **EXAMPLES**\n- **FILE MODES**\n- **FILES**\n- **SETUID USE**\n- **ENVIRONMENT**\n- **DIAGNOSTICS**\n- **IDENTIFICATION**\n- **SEE ALSO**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "CI", "section": "", "mode": "man", "summary": "ci - check in RCS revisions", "synopsis": "ci [options] file ...", "tldr_summary": "Check in RCS revisions (store file changes in the Revision Control System).", "tldr_examples": [ { "description": "Check in a file and keep the working file unlocked", "command": "ci -u {{path/to/file}}" }, { "description": "Check in a file and keep the working file locked", "command": "ci -l {{path/to/file}}" }, { "description": "Check in a file with a specific log message", "command": "ci -m\"{{log_message}}\" {{path/to/file}}" }, { "description": "Check in a file, unlocking it but leaving the working file read-only", "command": "ci {{path/to/file}}" }, { "description": "Force check-in even if there are no changes", "command": "ci -f -u {{path/to/file}}" } ], "tldr_source": "official", "flags": [ { "flag": "-r", "long": null, "arg": null, "description": "" }, { "flag": "-r", "long": null, "arg": null, "description": "RCS commands, a bare -r option specifies the most recent revision on the default branch, but with ci, a bare -r option reestablishes the default behavior of releasing a lock and removing the working file, and is used to override any default -l or -u op‐ tions established by shell aliases or scripts." }, { "flag": "-l", "long": null, "arg": null, "description": "works like -r, except it performs an additional co -l for the deposited revision. Thus, the deposited revision is immediately checked out again and locked. This is useful for saving a revision although one wants to continue editing it after the checkin." }, { "flag": "-u", "long": null, "arg": null, "description": "works like -l, except that the deposited revision is not locked. This lets one read the working file immediately after checkin. The -l, bare -r, and -u options are mutually exclusive and silently override each other. For example, ci -u -r is equivalent to ci -r because bare -r overrides -u." }, { "flag": "-f", "long": null, "arg": null, "description": "forces a deposit; the new revision is deposited even it is not different from the pre‐ ceding one." }, { "flag": "-k", "long": null, "arg": null, "description": "searches the working file for keyword values to determine its revision number, cre‐ ation date, state, and author (see co(1)), and assigns these values to the deposited revision, rather than computing them locally. It also generates a default login mes‐ sage noting the login of the caller and the actual checkin date. This option is use‐ ful for software distribution. A revision that is sent to several sites should be checked in with the -k option at these sites to preserve the original number, date, author, and state. The extracted keyword values and the default log message can be overridden with the options -d, -m, -s, -w, and any option that carries a revision number." }, { "flag": "-q", "long": null, "arg": null, "description": "quiet mode; diagnostic output is not printed. A revision that is not different from the preceding one is not deposited, unless -f is given." }, { "flag": "-i", "long": null, "arg": null, "description": "initial checkin; report an error if the RCS file already exists. This avoids race conditions in certain applications." }, { "flag": "-j", "long": null, "arg": null, "description": "just checkin and do not initialize; report an error if the RCS file does not already exist." }, { "flag": "-I", "long": null, "arg": null, "description": "interactive mode; the user is prompted and questioned even if the standard input is not a terminal." }, { "flag": "-d", "long": null, "arg": null, "description": "uses date for the checkin date and time. The date is specified in free format as ex‐ plained in co(1). This is useful for lying about the checkin date, and for -k if no date is available. If date is empty, the working file's time of last modification is used." }, { "flag": "-M", "long": null, "arg": null, "description": "Set the modification time on any new working file to be the date of the retrieved re‐ vision. For example, ci -d -M -u f does not alter f's modification time, even if f's contents change due to keyword substitution. Use this option with care; it can con‐ fuse make(1)." }, { "flag": "-m", "long": null, "arg": null, "description": "uses the string msg as the log message for all revisions checked in. If msg is omit‐ ted, it defaults to \"* empty log message *\". By convention, log messages that start with # are comments and are ignored by programs like GNU Emacs's vc package. Also, log messages that start with {clumpname} (followed by white space) are meant to be clumped together if possible, even if they are associated with different files; the {clumpname} label is used only for clumping, and is not considered to be part of the log message itself." }, { "flag": "-n", "long": null, "arg": null, "description": "error message if name is already assigned to another number." }, { "flag": "-n", "long": null, "arg": null, "description": "" }, { "flag": "-s", "long": null, "arg": null, "description": "sets the state of the checked-in revision to the identifier state. The default state is Exp." }, { "flag": "-t", "long": null, "arg": null, "description": "ing the existing text. The file cannot begin with -." }, { "flag": "", "long": null, "arg": null, "description": "Write descriptive text from the string into the RCS file, deleting the existing text. The -t option, in both its forms, has effect only during an initial checkin; it is silently ignored otherwise. During the initial checkin, if -t is not given, ci obtains the text from standard in‐ put, terminated by end-of-file or by a line containing . by itself. The user is prompted for the text if interaction is possible; see -I. For backward compatibility with older versions of RCS, a bare -t option is ignored." }, { "flag": "-T", "long": null, "arg": null, "description": "the latter and there is a new revision; preserve the RCS file's modification time oth‐ erwise. If you have locked a revision, ci usually updates the RCS file's modification time to the current time, because the lock is stored in the RCS file and removing the lock requires changing the RCS file. This can create an RCS file newer than the work‐ ing file in one of two ways: first, ci -M can create a working file with a date before the current time; second, when reverting to the previous revision the RCS file can change while the working file remains unchanged. These two cases can cause excessive recompilation caused by a make(1) dependency of the working file on the RCS file. The -T option inhibits this recompilation by lying about the RCS file's date. Use this option with care; it can suppress recompilation even when a checkin of one working file should affect another working file associated with the same RCS file. For exam‐ ple, suppose the RCS file's time is 01:00, the (changed) working file's time is 02:00, some other copy of the working file has a time of 03:00, and the current time is 04:00. Then ci -d -T sets the RCS file's time to 02:00 instead of the usual 04:00; this causes make(1) to think (incorrectly) that the other copy is newer than the RCS file." }, { "flag": "-w", "long": null, "arg": null, "description": "uses login for the author field of the deposited revision. Useful for lying about the author, and for -k if no author is available." }, { "flag": "-V", "long": null, "arg": null, "description": "" }, { "flag": "-V", "long": null, "arg": null, "description": "" }, { "flag": "-x", "long": null, "arg": null, "description": "specifies the suffixes for RCS files. A nonempty suffix matches any file name ending in the suffix. An empty suffix matches any file name of the form RCS/frag or frag1/RCS/frag2. The -x option can specify a list of suffixes separated by /. For example, -x,v/ specifies two suffixes: ,v and the empty suffix. If two or more suf‐ fixes are specified, they are tried in order when looking for an RCS file; the first one that works is used for that file. If no RCS file is found but an RCS file can be created, the suffixes are tried in order to determine the new RCS file's name. The default for suffixes is installation-dependent; normally it is ,v/ for hosts like Unix that permit commas in file names, and is empty (i.e. just the empty suffix) for other hosts." }, { "flag": "-z", "long": null, "arg": null, "description": "time zone for date in the -ddate option. The zone should be empty, a numeric UTC off‐ set, or the special string LT for local time. The default is an empty zone, which uses the traditional RCS format of UTC without any time zone indication and with slashes separating the parts of the date; otherwise, times are output in ISO 8601 for‐ mat with time zone indication. For example, if local time is January 11, 1990, 8pm Pacific Standard Time, eight hours west of UTC, then the time is output as follows: option time output" }, { "flag": "-z", "long": null, "arg": null, "description": "-zLT 1990-01-11 20:00:00-08 -z+05:30 1990-01-12 09:30:00+05:30 The -z option does not affect dates stored in RCS files, which are always UTC." } ], "examples": [ "Suppose ,v is an RCS suffix and the current directory contains a subdirectory RCS with an RCS", "file io.c,v. Then each of the following commands check in a copy of io.c into RCS/io.c,v as", "the latest revision, removing io.c.", "ci io.c; ci RCS/io.c,v; ci io.c,v;", "ci io.c RCS/io.c,v; ci io.c io.c,v;", "ci RCS/io.c,v io.c; ci io.c,v io.c;", "Suppose instead that the empty suffix is an RCS suffix and the current directory contains a", "subdirectory RCS with an RCS file io.c. The each of the following commands checks in a new", "revision.", "ci io.c; ci RCS/io.c;", "ci io.c RCS/io.c;", "ci RCS/io.c io.c;" ], "see_also": [ { "name": "co", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/co/1/json" }, { "name": "emacs", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/emacs/1/json" }, { "name": "ident", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/ident/1/json" }, { "name": "make", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/make/1/json" }, { "name": "rcs", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/rcs/1/json" }, { "name": "rcsclean", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/rcsclean/1/json" }, { "name": "rcsdiff", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/rcsdiff/1/json" }, { "name": "rcsmerge", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/rcsmerge/1/json" }, { "name": "rlog", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/rlog/1/json" }, { "name": "setuid", "section": "2", "url": "https://www.chedong.com/phpMan.php/man/setuid/2/json" }, { "name": "rcsfile", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/rcsfile/5/json" }, { "name": "info", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/info/1/json" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 31, "subsections": [ { "name": "-k -l -M -q -r -u", "lines": 28, "flag": "-u" } ] }, { "name": "OPTIONS", "lines": 1, "subsections": [ { "name": "-r", "lines": 1, "flag": "-r" }, { "name": "-r -r", "lines": 5, "flag": "-r" }, { "name": "-l", "lines": 5, "flag": "-l" }, { "name": "-u", "lines": 6, "flag": "-u" }, { "name": "-f", "lines": 3, "flag": "-f" }, { "name": "-k", "lines": 10, "flag": "-k" }, { "name": "-q", "lines": 3, "flag": "-q" }, { "name": "-i", "lines": 3, "flag": "-i" }, { "name": "-j", "lines": 3, "flag": "-j" }, { "name": "-I", "lines": 3, "flag": "-I" }, { "name": "-d", "lines": 5, "flag": "-d" }, { "name": "-M", "lines": 5, "flag": "-M" }, { "name": "-m", "lines": 8, "flag": "-m" }, { "name": "-n", "lines": 2, "flag": "-n" }, { "name": "-N -n", "lines": 1, "flag": "-n" }, { "name": "-s", "lines": 3, "flag": "-s" }, { "name": "-t", "lines": 2, "flag": "-t" }, { "name": "-t-", "lines": 11 }, { "name": "-T", "lines": 17, "flag": "-T" }, { "name": "-w", "lines": 3, "flag": "-w" }, { "name": "-V", "lines": 1, "flag": "-V" }, { "name": "-V", "lines": 1, "flag": "-V" }, { "name": "-x", "lines": 11, "flag": "-x" }, { "name": "-z", "lines": 8, "flag": "-z" }, { "name": "-z 1990/01/12 04:00:00 _(default)", "lines": 5, "flag": "-z" } ] }, { "name": "FILE NAMING", "lines": 23, "subsections": [] }, { "name": "EXAMPLES", "lines": 16, "subsections": [] }, { "name": "FILE MODES", "lines": 4, "subsections": [] }, { "name": "FILES", "lines": 31, "subsections": [] }, { "name": "SETUID USE", "lines": 54, "subsections": [] }, { "name": "ENVIRONMENT", "lines": 17, "subsections": [] }, { "name": "DIAGNOSTICS", "lines": 4, "subsections": [] }, { "name": "IDENTIFICATION", "lines": 6, "subsections": [] }, { "name": "SEE ALSO", "lines": 20, "subsections": [] } ], "sections": { "NAME": { "content": "ci - check in RCS revisions\n", "subsections": [] }, "SYNOPSIS": { "content": "ci [options] file ...\n", "subsections": [] }, "DESCRIPTION": { "content": "ci stores new revisions into RCS files. Each file name matching an RCS suffix is taken to be\nan RCS file. All others are assumed to be working files containing new revisions. ci de‐\nposits the contents of each working file into the corresponding RCS file. If only a working\nfile is given, ci tries to find the corresponding RCS file in an RCS subdirectory and then in\nthe working file's directory. For more details, see FILE NAMING below.\n\nFor ci to work, the caller's login must be on the access list, except if the access list is\nempty or the caller is the superuser or the owner of the file. To append a new revision to\nan existing branch, the tip revision on that branch must be locked by the caller. Otherwise,\nonly a new branch can be created. This restriction is not enforced for the owner of the file\nif non-strict locking is used (see rcs(1)). A lock held by someone else can be broken with\nthe rcs command.\n\nUnless the -f option is given, ci checks whether the revision to be deposited differs from\nthe preceding one. If not, instead of creating a new revision ci reverts to the preceding\none. To revert, ordinary ci removes the working file and any lock; ci -l keeps and ci -u re‐\nmoves any lock, and then they both generate a new working file much as if co -l or co -u had\nbeen applied to the preceding revision. When reverting, any -n and -s options apply to the\npreceding revision.\n\nFor each revision deposited, ci prompts for a log message. The log message should summarize\nthe change and must be terminated by end-of-file or by a line containing . by itself. If\nseveral files are checked in ci asks whether to reuse the previous log message. If the stan‐\ndard input is not a terminal, ci suppresses the prompt and uses the same log message for all\nfiles. See also -m.\n\nIf the RCS file does not exist, ci creates it and deposits the contents of the working file\nas the initial revision (default number: 1.1). The access list is initialized to empty. In‐\nstead of the log message, ci requests descriptive text (see -t below).\n\nThe number rev of the deposited revision can be given by any of the options -f, -i, -I, -j,", "subsections": [ { "name": "-k -l -M -q -r -u", "content": "must already be defined; see the -n and -N options for assigning names during checkin. If\nrev is $, ci determines the revision number from keyword values in the working file.\n\nIf rev begins with a period, then the default branch (normally the trunk) is prepended to it.\nIf rev is a branch number followed by a period, then the latest revision on that branch is\nused.\n\nIf rev is a revision number, it must be higher than the latest one on the branch to which rev\nbelongs, or must start a new branch.\n\nIf rev is a branch rather than a revision number, the new revision is appended to that\nbranch. The level number is obtained by incrementing the tip revision number of that branch.\nIf rev indicates a non-existing branch, that branch is created with the initial revision num‐\nbered rev.1.\n\nIf rev is omitted, ci tries to derive the new revision number from the caller's last lock.\nIf the caller has locked the tip revision of a branch, the new revision is appended to that\nbranch. The new revision number is obtained by incrementing the tip revision number. If the\ncaller locked a non-tip revision, a new branch is started at that revision by incrementing\nthe highest branch number at that revision. The default initial branch and level numbers are\n1.\n\nIf rev is omitted and the caller has no lock, but owns the file and locking is not set to\nstrict, then the revision is appended to the default branch (normally the trunk; see the -b\noption of rcs(1)).\n\nException: On the trunk, revisions can be appended to the end, but not inserted.\n", "flag": "-u" } ] }, "OPTIONS": { "content": "", "subsections": [ { "name": "-r", "content": "", "flag": "-r" }, { "name": "-r -r", "content": "RCS commands, a bare -r option specifies the most recent revision on the default\nbranch, but with ci, a bare -r option reestablishes the default behavior of releasing\na lock and removing the working file, and is used to override any default -l or -u op‐\ntions established by shell aliases or scripts.\n", "flag": "-r" }, { "name": "-l", "content": "works like -r, except it performs an additional co -l for the deposited revision.\nThus, the deposited revision is immediately checked out again and locked. This is\nuseful for saving a revision although one wants to continue editing it after the\ncheckin.\n", "flag": "-l" }, { "name": "-u", "content": "works like -l, except that the deposited revision is not locked. This lets one read\nthe working file immediately after checkin.\n\nThe -l, bare -r, and -u options are mutually exclusive and silently override each\nother. For example, ci -u -r is equivalent to ci -r because bare -r overrides -u.\n", "flag": "-u" }, { "name": "-f", "content": "forces a deposit; the new revision is deposited even it is not different from the pre‐\nceding one.\n", "flag": "-f" }, { "name": "-k", "content": "searches the working file for keyword values to determine its revision number, cre‐\nation date, state, and author (see co(1)), and assigns these values to the deposited\nrevision, rather than computing them locally. It also generates a default login mes‐\nsage noting the login of the caller and the actual checkin date. This option is use‐\nful for software distribution. A revision that is sent to several sites should be\nchecked in with the -k option at these sites to preserve the original number, date,\nauthor, and state. The extracted keyword values and the default log message can be\noverridden with the options -d, -m, -s, -w, and any option that carries a revision\nnumber.\n", "flag": "-k" }, { "name": "-q", "content": "quiet mode; diagnostic output is not printed. A revision that is not different from\nthe preceding one is not deposited, unless -f is given.\n", "flag": "-q" }, { "name": "-i", "content": "initial checkin; report an error if the RCS file already exists. This avoids race\nconditions in certain applications.\n", "flag": "-i" }, { "name": "-j", "content": "just checkin and do not initialize; report an error if the RCS file does not already\nexist.\n", "flag": "-j" }, { "name": "-I", "content": "interactive mode; the user is prompted and questioned even if the standard input is\nnot a terminal.\n", "flag": "-I" }, { "name": "-d", "content": "uses date for the checkin date and time. The date is specified in free format as ex‐\nplained in co(1). This is useful for lying about the checkin date, and for -k if no\ndate is available. If date is empty, the working file's time of last modification is\nused.\n", "flag": "-d" }, { "name": "-M", "content": "Set the modification time on any new working file to be the date of the retrieved re‐\nvision. For example, ci -d -M -u f does not alter f's modification time, even if f's\ncontents change due to keyword substitution. Use this option with care; it can con‐\nfuse make(1).\n", "flag": "-M" }, { "name": "-m", "content": "uses the string msg as the log message for all revisions checked in. If msg is omit‐\nted, it defaults to \"* empty log message *\". By convention, log messages that\nstart with # are comments and are ignored by programs like GNU Emacs's vc package.\nAlso, log messages that start with {clumpname} (followed by white space) are meant to\nbe clumped together if possible, even if they are associated with different files; the\n{clumpname} label is used only for clumping, and is not considered to be part of the\nlog message itself.\n", "flag": "-m" }, { "name": "-n", "content": "error message if name is already assigned to another number.\n", "flag": "-n" }, { "name": "-N -n", "content": "", "flag": "-n" }, { "name": "-s", "content": "sets the state of the checked-in revision to the identifier state. The default state\nis Exp.\n", "flag": "-s" }, { "name": "-t", "content": "ing the existing text. The file cannot begin with -.\n", "flag": "-t" }, { "name": "-t-", "content": "Write descriptive text from the string into the RCS file, deleting the existing text.\n\nThe -t option, in both its forms, has effect only during an initial checkin; it is\nsilently ignored otherwise.\n\nDuring the initial checkin, if -t is not given, ci obtains the text from standard in‐\nput, terminated by end-of-file or by a line containing . by itself. The user is\nprompted for the text if interaction is possible; see -I.\n\nFor backward compatibility with older versions of RCS, a bare -t option is ignored.\n" }, { "name": "-T", "content": "the latter and there is a new revision; preserve the RCS file's modification time oth‐\nerwise. If you have locked a revision, ci usually updates the RCS file's modification\ntime to the current time, because the lock is stored in the RCS file and removing the\nlock requires changing the RCS file. This can create an RCS file newer than the work‐\ning file in one of two ways: first, ci -M can create a working file with a date before\nthe current time; second, when reverting to the previous revision the RCS file can\nchange while the working file remains unchanged. These two cases can cause excessive\nrecompilation caused by a make(1) dependency of the working file on the RCS file. The\n-T option inhibits this recompilation by lying about the RCS file's date. Use this\noption with care; it can suppress recompilation even when a checkin of one working\nfile should affect another working file associated with the same RCS file. For exam‐\nple, suppose the RCS file's time is 01:00, the (changed) working file's time is 02:00,\nsome other copy of the working file has a time of 03:00, and the current time is\n04:00. Then ci -d -T sets the RCS file's time to 02:00 instead of the usual 04:00;\nthis causes make(1) to think (incorrectly) that the other copy is newer than the RCS\nfile.\n", "flag": "-T" }, { "name": "-w", "content": "uses login for the author field of the deposited revision. Useful for lying about the\nauthor, and for -k if no author is available.\n", "flag": "-w" }, { "name": "-V", "content": "", "flag": "-V" }, { "name": "-V", "content": "", "flag": "-V" }, { "name": "-x", "content": "specifies the suffixes for RCS files. A nonempty suffix matches any file name ending\nin the suffix. An empty suffix matches any file name of the form RCS/frag or\nfrag1/RCS/frag2. The -x option can specify a list of suffixes separated by /. For\nexample, -x,v/ specifies two suffixes: ,v and the empty suffix. If two or more suf‐\nfixes are specified, they are tried in order when looking for an RCS file; the first\none that works is used for that file. If no RCS file is found but an RCS file can be\ncreated, the suffixes are tried in order to determine the new RCS file's name. The\ndefault for suffixes is installation-dependent; normally it is ,v/ for hosts like Unix\nthat permit commas in file names, and is empty (i.e. just the empty suffix) for other\nhosts.\n", "flag": "-x" }, { "name": "-z", "content": "time zone for date in the -ddate option. The zone should be empty, a numeric UTC off‐\nset, or the special string LT for local time. The default is an empty zone, which\nuses the traditional RCS format of UTC without any time zone indication and with\nslashes separating the parts of the date; otherwise, times are output in ISO 8601 for‐\nmat with time zone indication. For example, if local time is January 11, 1990, 8pm\nPacific Standard Time, eight hours west of UTC, then the time is output as follows:\n\noption time output", "flag": "-z" }, { "name": "-z 1990/01/12 04:00:00 _(default)", "content": "-zLT 1990-01-11 20:00:00-08\n-z+05:30 1990-01-12 09:30:00+05:30\n\nThe -z option does not affect dates stored in RCS files, which are always UTC.\n", "flag": "-z" } ] }, "FILE NAMING": { "content": "Pairs of RCS files and working files can be specified in three ways (see also the example\nsection).\n\n1) Both the RCS file and the working file are given. The RCS file name is of the form\nfrag1/workfileX and the working file name is of the form frag2/workfile where frag1/ and\nfrag2/ are (possibly different or empty) file names, workfile is a file name, and X is an RCS\nsuffix. If X is empty, frag1/ must start with RCS/ or must contain /RCS/.\n\n2) Only the RCS file is given. Then the working file is created in the current directory and\nits name is derived from the RCS file name by removing frag1/ and the suffix X.\n\n3) Only the working file is given. Then ci considers each RCS suffix X in turn, looking for\nan RCS file of the form frag2/RCS/workfileX or (if the former is not found and X is nonempty)\nfrag2/workfileX.\n\nIf the RCS file is specified without a file name in 1) and 2), ci looks for the RCS file\nfirst in the directory ./RCS and then in the current directory.\n\nci reports an error if an attempt to open an RCS file fails for an unusual reason, even if\nthe RCS file's name is just one of several possibilities. For example, to suppress use of\nRCS commands in a directory d, create a regular file named d/RCS so that casual attempts to\nuse RCS commands in d fail because d/RCS is not a directory.\n", "subsections": [] }, "EXAMPLES": { "content": "Suppose ,v is an RCS suffix and the current directory contains a subdirectory RCS with an RCS\nfile io.c,v. Then each of the following commands check in a copy of io.c into RCS/io.c,v as\nthe latest revision, removing io.c.\n\nci io.c; ci RCS/io.c,v; ci io.c,v;\nci io.c RCS/io.c,v; ci io.c io.c,v;\nci RCS/io.c,v io.c; ci io.c,v io.c;\n\nSuppose instead that the empty suffix is an RCS suffix and the current directory contains a\nsubdirectory RCS with an RCS file io.c. The each of the following commands checks in a new\nrevision.\n\nci io.c; ci RCS/io.c;\nci io.c RCS/io.c;\nci RCS/io.c io.c;\n", "subsections": [] }, "FILE MODES": { "content": "An RCS file created by ci inherits the read and execute permissions from the working file.\nIf the RCS file exists already, ci preserves its read and execute permissions. ci always\nturns off all write permissions of RCS files.\n", "subsections": [] }, "FILES": { "content": "Temporary files are created in the directory containing the working file, and also in the\ntemporary directory (see TMPDIR under ENVIRONMENT). A semaphore file or files are created in\nthe directory containing the RCS file. With a nonempty suffix, the semaphore names begin\nwith the first character of the suffix; therefore, do not specify an suffix whose first char‐\nacter could be that of a working file name. With an empty suffix, the semaphore names end\nwith so working file names should not end in .\n\nci never changes an RCS file or working file. Normally, ci unlinks the file and creates a\nnew one; but instead of breaking a chain of one or more symbolic links to an RCS file, it un‐\nlinks the destination file instead. Therefore, ci breaks any hard or symbolic links to any\nworking file it changes; and hard links to RCS files are ineffective, but symbolic links to\nRCS files are preserved.\n\nThe effective user must be able to search and write the directory containing the RCS file.\nNormally, the real user must be able to read the RCS and working files and to search and\nwrite the directory containing the working file; however, some older hosts cannot easily\nswitch between real and effective users, so on these hosts the effective user is used for all\naccesses. The effective user is the same as the real user unless your copies of ci and co\nhave setuid privileges. As described in the next section, these privileges yield extra secu‐\nrity if the effective user owns all RCS files and directories, and if only the effective user\ncan write RCS directories.\n\nUsers can control access to RCS files by setting the permissions of the directory containing\nthe files; only users with write access to the directory can use RCS commands to change its\nRCS files. For example, in hosts that allow a user to belong to several groups, one can make\na group's RCS directories writable to that group only. This approach suffices for informal\nprojects, but it means that any group member can arbitrarily change the group's RCS files,\nand can even remove them entirely. Hence more formal projects sometimes distinguish between\nan RCS administrator, who can change the RCS files at will, and other project members, who\ncan check in new revisions but cannot otherwise change the RCS files.\n", "subsections": [] }, "SETUID USE": { "content": "To prevent anybody but their RCS administrator from deleting revisions, a set of users can\nemploy setuid privileges as follows.\n\n• Check that the host supports RCS setuid use. Consult a trustworthy expert if there are any\ndoubts. It is best if the seteuid system call works as described in Posix 1003.1a Draft 5,\nbecause RCS can switch back and forth easily between real and effective users, even if the\nreal user is root. If not, the second best is if the setuid system call supports saved se‐\ntuid (the {POSIXSAVEDIDS} behavior of Posix 1003.1-1990); this fails only if the real or\neffective user is root. If RCS detects any failure in setuid, it quits immediately.\n\n• Choose a user A to serve as RCS administrator for the set of users. Only A can invoke the\nrcs command on the users' RCS files. A should not be root or any other user with special\npowers. Mutually suspicious sets of users should use different administrators.\n\n• Choose a file name B to be a directory of files to be executed by the users.\n\n• Have A set up B to contain copies of ci and co that are setuid to A by copying the commands\nfrom their standard installation directory D as follows:\n\nmkdir B\ncp D/c[io] B\nchmod go-w,u+s B/c[io]\n\n• Have each user prepend B to their command search path as follows:\n\nPATH=B:$PATH; export PATH # ordinary shell\nset path=(B $path) # C shell\n\n• Have A create each RCS directory R with write access only to A as follows:\n\nmkdir R\nchmod go-w R\n\n• If you want to let only certain users read the RCS files, put the users into a group G, and\nhave A further protect the RCS directory as follows:\n\nchgrp G R\nchmod g-w,o-rwx R\n\n• Have A copy old RCS files (if any) into R, to ensure that A owns them.\n\n• An RCS file's access list limits who can check in and lock revisions. The default access\nlist is empty, which grants checkin access to anyone who can read the RCS file. If you\nwant limit checkin access, have A invoke rcs -a on the file; see rcs(1). In particular,\nrcs -e -aA limits access to just A.\n\n• Have A initialize any new RCS files with rcs -i before initial checkin, adding the -a op‐\ntion if you want to limit checkin access.\n\n• Give setuid privileges only to ci, co, and rcsclean; do not give them to rcs or to any\nother command.\n\n• Do not use other setuid commands to invoke RCS commands; setuid is trickier than you think!\n", "subsections": [] }, "ENVIRONMENT": { "content": "RCSINIT\nOptions prepended to the argument list, separated by spaces. A backslash escapes spa‐\nces within an option. The RCSINIT options are prepended to the argument lists of most\nRCS commands. Useful RCSINIT options include -q, -V, -x, and -z.\n\nRCSMEMLIMIT\nNormally, for speed, commands either memory map or copy into memory the RCS file if\nits size is less than the memory-limit, currently defaulting to ``unlimited''. Other‐\nwise (or if the initially-tried speedy ways fail), the commands fall back to using\nstandard i/o routines. You can adjust the memory limit by setting RCSMEMLIMIT to a\nnumeric value lim (measured in kilobytes). An empty value is silently ignored. As a\nside effect, specifying RCSMEMLIMIT inhibits fall-back to slower routines.\n\nTMPDIR Name of the temporary directory. If not set, the environment variables TMP and TEMP\nare inspected instead and the first value found is taken; if none of them are set, a\nhost-dependent default is used, typically /tmp.\n", "subsections": [] }, "DIAGNOSTICS": { "content": "For each revision, ci prints the RCS file, the working file, and the number of both the de‐\nposited and the preceding revision. The exit status is zero if and only if all operations\nwere successful.\n", "subsections": [] }, "IDENTIFICATION": { "content": "Author: Walter F. Tichy.\nManual Page Revision: 5.10.1; Release Date: 2022-02-19.\nCopyright © 2010-2022 Thien-Thi Nguyen.\nCopyright © 1990, 1991, 1992, 1993, 1994, 1995 Paul Eggert.\nCopyright © 1982, 1988, 1989 Walter F. Tichy.\n", "subsections": [] }, "SEE ALSO": { "content": "co(1), emacs(1), ident(1), make(1), rcs(1), rcsclean(1), rcsdiff(1), rcsmerge(1), rlog(1),\nsetuid(2), rcsfile(5).\n\nWalter F. Tichy, RCS--A System for Version Control, Software--Practice & Experience 15, 7\n(July 1985), 637-654.\n\nThe full documentation for RCS is maintained as a Texinfo manual. If the info(1) and RCS\nprograms are properly installed at your site, the command\n\ninfo rcs\n\nshould give you access to the complete manual. Additionally, the RCS homepage:\n\nhttp://www.gnu.org/software/rcs/\n\nhas news and links to the latest release, development site, etc.\n\n\n\nGNU RCS 5.10.1 2022-02-19 CI(1)", "subsections": [] } } } }