.\" .\" aegis - project change supervisor .\" Copyright (C) 1999 Peter Miller; .\" All rights reserved. .\" .\" This program is free software; you can redistribute it and/or modify .\" it under the terms of the GNU General Public License as published by .\" the Free Software Foundation; either version 2 of the License, or .\" (at your option) any later version. .\" .\" This program is distributed in the hope that it will be useful, .\" but WITHOUT ANY WARRANTY; without even the implied warranty of .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the .\" GNU General Public License for more details. .\" .\" You should have received a copy of the GNU General Public License .\" along with this program; if not, write to the Free Software .\" Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111, USA. .\" .\" MANIFEST: document describing lib/en/man1/z_aliass .\" .SS Example Aliases may be used in may ways. The most common is to give a particular release a code name. You would do this by saying .RS .ft CW aenpa example.4.2 sydney .ft R .RE This would make ``sydney'' an alias for the ``example.4.2'' branch. .PP Another use for aliases is to have a fixed alias for your active branch, so that your developer team does not need to change their default project, even though the branch number moves on for each release. You could say .RS .ft CW aenpa example.4.2 example.cur .ft R .RE This would make ``example.cur'' an alias for the ``example.4.2'' branch. When this was finished, and 4.3 started, a project administrator could say .RS .ft CW aerpa example.cur .br aenpa example.4.2 example.cur .ft R .RE Now ``example.cur'' is an alias for the ``example.4.3'' branch, but the developers need only reference ``example.cur'' to always work on the right branch.