diff options
| author | cjep <cjep> | 2003-06-07 14:58:29 +0000 |
|---|---|---|
| committer | cjep <cjep> | 2003-06-07 14:58:29 +0000 |
| commit | cc45a5a6803a27016414f6b734013786ba31e5f4 (patch) | |
| tree | b0a46c5fa9b90204b8ddbe28abaef8eee31eaf05 /devel | |
| parent | 545d4e6d6edc4ae62a4211fe21e3373324f62185 (diff) | |
| download | pkgsrc-cc45a5a6803a27016414f6b734013786ba31e5f4.tar.gz | |
Truncate to <=24 lines
Diffstat (limited to 'devel')
| -rw-r--r-- | devel/aegis/DESCR | 13 |
1 files changed, 1 insertions, 12 deletions
diff --git a/devel/aegis/DESCR b/devel/aegis/DESCR index bd0e9162e60..3fbf6ed37a3 100644 --- a/devel/aegis/DESCR +++ b/devel/aegis/DESCR @@ -10,18 +10,7 @@ which is being edited directly by the developers - there are O(n!) interactions between developers - this makes adding "just one more" developer a potential disaster. -Another win is that the project baseline always works. Always -having a working baseline means that a version is always available -for demonstrations, or those "pre-release snapshots" we are always -forced to provide. - -The above advantages are all very well - for management types. -Why should Joe Average Programmer use Aegis? Recall that RCS provides -file locking, but only for one file at a time. Aegis provides the -file locking, atomically, for the set of files in the change. -Recall also that RCS locks the file the instant you start editing -it. This makes popular files a project bottleneck. Aegis allows -concurrent editing, and a resolution mechanism just before the +Aegis allows concurrent editing, and a resolution mechanism just before the change must be integrated, meaning fewer delays for J.A.Programmer. Aegis also has strong support for geographically distributed |