From 7c8897305807c80f420e0d77eb7f6c926a35c2cb Mon Sep 17 00:00:00 2001 From: cjep Date: Sat, 7 Jun 2003 14:58:29 +0000 Subject: Truncate to <=24 lines --- devel/aegis/DESCR | 13 +------------ 1 file changed, 1 insertion(+), 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 -- cgit v1.2.3