On Thu, Mar 13, 2003 at 02:40:31PM -0500, Kuba Ober wrote: > Well, each change that you create with aenc or tkaenc gets a number. Usually, > there should be a change for each confirmed bug report at least. The job of > creating changes is quite separate from the job of actually developing the > changes. You can have different people doing creation of the changes, and > different ones doing development.
Hm. Ok. Let's count keystrokes for a minimalistic real life example. Let's suppose Angus told me there is a space missing in inset/insetenv.C. I do cvs up vi insets/insetenv.C [insert the space] :wq vi insets/Changelog [insert changelog] cvs commit [write 'Fix for missing space as reported by Angus] :wq The "cvs overhead" is 'cvs up' + 'cvs commit', i.e. 18 keystrokes. What would be the corresponding aegis version? > One of significant drawbacks of CVS is that it effectively prevents you from > sharing your work in progress Which, in an ideal world, is not much of a problem, as changes should be small and self-contained. LyX, of course, is not the ideal world... Ok, maybe aegis is really better in large projects, but I don't think, LyX reaches that critical mass. This was btw my impression when we used aegis in our two-or-three-person-project I mentioned earlier. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
