On Thu, Mar 13, 2003 at 02:12:07PM -0500, Kuba Ober wrote: > I was very explicit about things. First of all, if you are wearing all the > hats yourself -- you're a developer, reviewer and administrator of the > project, the only thing you need to do to make a new change and integrate it > to the master server is:
This is about 10 lines too long. > $ ae_p lyx.1.4.1 > # once per login, and only if there are many projects; the msot recent branch > of the first project is a default what is a login ? > $ tkaenc > # a gui pops up and lets you type a change information Waste of time - gets in my way. Maybe I don't even know what I'm going to do. > $ ae_c 110 > # okay, we choose to work on change number 110 what on earth ... ? > $ aedb > # begin development > $ aecd; aecp README > # add the README file into the change I seriously have to do this for every file I want to edit ? > $ vi README > # do the changes (you could use any editor, obviously) > $ aed && aeb && aede > # build and finish development -- note that build here will do nothing, as > # compilation results are in the repository too [managed automatically > # by Aegis] > $ aerpass > # make the review pass > $ cd ~; aed && aeb && aeipass > # build and integrate into the baseline for given branch I assume you can turn this stuff off. > $ aedist -send | mail -s integrate [EMAIL PROTECTED] > # upload to the server which should handle the rest automagically Anyway I'm not sure a discussion on Aegis is relevant or fruitful :) john
