Chapter 2. Cheat Sheet

Table of Contents

1. Common Commands
2. Developer Commands
3. Reviewer Commands
4. Integrator Commands
5. Project Administrator Commands

This page is a quick reference into the common Aegis commands.

1. Common Commands

ae_p project-name.branch-number

Set current project number for all following Aegis commands. The ae_p command with no arguments will `unset' this forced default.

ae_c number

Set current change number for all following Aegis commands. The ae_c command with no arguments will `unset' this forced default.

aecd [ -bl ]

Change directory [change to baseline].


Aegis build - used by developers, reviewers and/ or integrators.


Run tests - used by developers.


Difference of change files with baseline.


View difference files generated with aed.

ael cd

List change details.

aeca [ -l ]

Edit [list] change attributes.


Create a new change (see aenc(1) for details), using a GUI interface. This makes it a damn sight easier to type in the description field.


Edit change attributes (see aeca(1) for details), using a GUI interface. This makes it a damn sight easier to edit the description field.

ael ll

List all of the lists (there are a lot).

ael c

List all of the changes for a project (branch).

ael cf

List all of the files in a change.


This is a man page documenting the ~/.aegisrc file format.

2. Developer Commands

Procedure: ael cd aedb do stuff aeb aet aed aedless [ aeclean ] aede


Develop begin [undo].


Develop end [undo].


This will remove all files in the development directory which are not in the change as new files or copied files. This may delete files that you want, so be careful.

The aeclean(1) command uses Aegis' knowledge of what is supposed to be in the change. You are meant to tell Aegis about all source files you create in a development directory. If you have forgotten to do this, it is highly likely that the integration would fail in any case.

If you are importing files from elsewhere, use “aenf .” and all of the files in the directory tree below dot (the current directory) will be added to the change (make sure there are no object files when you do this).


Prepares a file in the project for editing within the change; i.e. copy file into change from baseline. Remove symlink if necessary, etc.


Reverse the effects of the above.

aecpu -unch

Will check all files in your change to see if any have not been modified, and perform an aecpu on them. This will stop an unnecessary version number increment for files that have not changed. (And also improves test correlations.)


Merge out-of-date files. See the -Only-merge option of the aed(1) command.


Create/ add a new file [undo].


Rename (move) files.


This tells Aegis the file is to be removed from the baseline when the change is integrated. Or aermu to undo this before the change is finished.

3. Reviewer Commands

Procedure: ael cd aecd aedless view output, review source files -> aerpass

Remember: the point of reviews is to find problems, not be a rubber stamp. You are expected to fail some reviews.


Review pass.


Review pass undo.


Review fail.

4. Integrator Commands

Procedure: aeib aeb aet aed aeipass

There is an aeintegratq(1) script distributed with Aegis to do this procedure automatically.


Integrate begin [undo].


Integrate pass.


Integrate fail.

5. Project Administrator Commands

This includes all of the commands that don't fit the categories above.


Create a new change [undo]. See aecattr(5) for description of file format, or use tkaenc(1) instead.

aend and aerd

New developer; remove developer.

aenrv and aerrv

New reviewer; remover reviewer.

aeni and aeri

New integrator; remove integrator.

aena and aera

New (project) administrator; remove administrator.

aepa [-l]

Edit [list] project attributes (see aepattr(5) for file format).

aeca [-l]

Edit [list] change attributes (see aecattr(5) for file format).


Edit change attributes using a GUI. This makes it much easier to type in the description field.