Rcs: Difference between revisions
From DWIKI
mNo edit summary |
mNo edit summary |
||
| Line 3: | Line 3: | ||
<blockquote>The Revision Control System (RCS) manages multiple revisions of files. RCS automates the storing, retrieval, logging, identification, and merging of revisions. RCS is useful for text that is revised frequently, including source code, programs, documentation, graphics, papers, and form letters.</blockquote> | <blockquote>The Revision Control System (RCS) manages multiple revisions of files. RCS automates the storing, retrieval, logging, identification, and merging of revisions. RCS is useful for text that is revised frequently, including source code, programs, documentation, graphics, papers, and form letters.</blockquote> | ||
- | =HOWTO= | ||
==Create repository== | |||
mkdir RCS | |||
==Check in file== | |||
ci -l foo | |||
==Show history== | |||
rcs show foo | |||
Currently RCS isn't used much anymore for "regular" revision control but comes in quite handy when you need to keep versions but have no need for an extensive external repository. | Currently RCS isn't used much anymore for "regular" revision control but comes in quite handy when you need to keep versions but have no need for an extensive external repository. | ||
Revision as of 15:56, 16 June 2022
Revision Control System
From the GNU site:
The Revision Control System (RCS) manages multiple revisions of files. RCS automates the storing, retrieval, logging, identification, and merging of revisions. RCS is useful for text that is revised frequently, including source code, programs, documentation, graphics, papers, and form letters.
HOWTO
Create repository
mkdir RCS
Check in file
ci -l foo
Show history
rcs show foo
Currently RCS isn't used much anymore for "regular" revision control but comes in quite handy when you need to keep versions but have no need for an extensive external repository.
FAQ
RCS: no lock set by
rename/copy the file, co -l filename, and overwrite it with the saved copy
