5
http://prcs.sourceforge.net/
7
* No network support; no Windows or Mac support.
9
* Long-lived file IDs, generated from . Files can be reintroduced
10
after they are deleted.
14
* Custom keyword replacement: can specify keywords such as the release
15
number. Commands to update keywords, and to strip them out.
16
Separate ``rekey`` command can be used after a checkin to bring
19
* Users are allowed to edit the manifest file, which also contains
20
some system-maintained data. This apparently works OK but I think
21
it makes people uncomfotable.
23
* ``populate`` command adds all unversioned files and unregister files
24
which are no longer present.
26
* Merge algorithm is similar to the best-parent three-way merge we're
27
planning on using; in particular it remembers merged parents to help
30
* ``$Format$`` feature useful in generating arbitrary tags inside text,
33
/* $Format: "static char* version = \"$ProjectVersion$\";"$ */
34
static char* version = "x.x";
38
/* $Format: "static char* version = \"$ProjectVersion$\";"$ */
39
static char* version = "1.2";
41
Also a good bundle of other keywords.
43
* ``prcs execute`` is like find-xargs; perhaps easier to have a
46
__ http://svn.haxx.se/dev/archive-2004-12/1065.shtml
49
Should have a look at their storage format; probably pretty efficient.
b'\\ No newline at end of file'
added
removed
doc/compared-prcs.txt
