> 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?
[invoke whatever script you have to sync with the master -- it depends on the setup, obviously it's a single command] aenc [write 'Fix for the missing space as reported by Angus] ae_c xxx [choose the change you've just created] aecp insets/insetenv.C vi insets/insetenv.C [insert the space] aeb && aed && aede aerpass aeib && aeb && aed && aeipass [invoke whatever other script to sync with the master again] Note that aeb && aed && aede are trivial to put into a single alias (the aexxxx stuff are aliases for aegis -xxxxx anyway), just as aeib && aeb && aed && aeipass are If you are really that conscious about the number of keystrokes that you do, it's trivial enough to have say an "aetriviale" alias which wraps up the change all the way to the repository (as in building, passing review, integrating, syncing integration to the rep). > > 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... No matter how small or "insignificant" a change is, there should be a way to review it without having to post a patch to the mailing list. And the fact that a change either passed review or was rejected should be documented so that is accessible. Although mailing lists are commonplace to do that, it's not the correct approach. A database which keeps all that information is simply provided with Aegis, it comes for free, there is a read-only web interface for Aegis that comes by default with Aegis itself. > Ok, maybe aegis is really better in large projects, but I don't think, LyX > reaches that critical mass. I use it for a 13k line project of mine (among others). I also use it for a webpage structure that has about 500kb of text. I also use it for DNS, which has about 30k in config and domain files all together. > This was btw my impression when we used aegis > in our two-or-three-person-project I mentioned earlier. I don't think that keeping a well accessible record of what was done, when and by whom is something that small projects can simply ignore. It also has the added benefit that one teaches himself some self-discipline. I guess it would even look good on the resume. Cheers, Kuba Ober
