Next: [[cvs: File permissions#File permissions|File permissions]], Up: [[cvs: How data is stored in the repository#How data is stored in the repository|Repository storage]] |[[cvs: Index#SEC_Contents|Contents]]||[[cvs: Index#Index|Index]]|
,v
’
appended to the end. Here is what the repository for
the ‘yoyodyne/tc’ directory might look like:
$CVSROOT
|
+--yoyodyne
| |
| +--tc
| | |
+--Makefile,v
+--backend.c,v
+--driver.c,v
+--frontend.c,v
+--parser.c,v
+--man
| |
| +--tc.1,v
|
+--testing
|
+--testpgm.t,v
+--test2.t,v
man
page
rcsfile(5), distributed with RCS, or the
file ‘doc/RCSFILES’ in the CVS source
distribution. This
file format has become very common—many systems other
than CVS or RCS can at least import history
files in this format.
The RCS files used in CVS differ in a few
ways from the standard format. The biggest difference
is magic branches; for more information see [[cvs: Magic branch numbers#Magic branch numbers|Magic branch numbers]]. Also in CVS the valid tag names
are a subset of what RCS accepts; for CVS’s
rules see [[cvs: Tags-Symbolic revisions#Tags–Symbolic revisions|Tags]].
----
Next: [[cvs: File permissions#File permissions|File permissions]], Up: [[cvs: How data is stored in the repository#How data is stored in the repository|Repository storage]] |[[cvs: Index#SEC_Contents|Contents]]||[[cvs: Index#Index|Index]]|