CVS
A CVS repository of Quagga is available. The repository is accessible through anonymous CVS. You will need recent versions of the GNU auto* tools to build from the CVS tree. Run update-autotools to generate the neccessary build files, including the configure script. Alternatively, use a snapshot as these come with the configure script already built and should not require auto* tools to be installed.
-
CVS details:
- CVS Root: :pserver:anoncvs@anoncvs.quagga.net:/var/cvsroot
- Module: quagga
- Password: NULL, blank, nada, no password
-
Example:
$ cvs -d :pserver:anoncvs@anoncvs.quagga.net:/var/cvsroot login Logging in to :pserver:anoncvs@anoncvs.quagga.net:2401/var/cvsroot CVS password: # (no password - hit return) $ cvs -d :pserver:anoncvs@anoncvs.quagga.net:/var/cvsroot co quagga
- web interface to CVS.
- Daily CVS snapshots
- Commit list
- Alternative commit list, includes diff's of each change, and tracks both GNU zebra and Quagga.
-
The CVS tree is also accessible
via
Subversion.
The SVN mirror is provided by Datacore.
- Quagga git repository, synced with CVS on ocassion. Further git repositories are also available. A gitweb interface is also available, and makes for easy browsing of the history of the Quagga sourcebase.
Submitting patches
Bug fixes, features and patches in general are most welcome. Please send them to the Quagga development list (note you probably will need to subscribe first). The maintainers are can be contacted either via the lists or at maintainers@quagga.net. The lists are the preferred contact point for general issues/topics, please only email the maintainer address for issues which *must* remain private. Please see the "contact us" page for further details on communicating with the maintainers.
Please read the HACKING document in CVS and bear these in mind when submitting patches. Some of the more immediately relevant points are covered below.
Note that the preferred form for patches is in unified context diff format, as produced by:
diff -upwb
or
cvs -q -z diff -uwb
if using CVS.
Please make patches relative to the top level directory, or above. Extra brownie points will be given to those whose patches also update ChangeLog file(s) with appropriate messages detailling the changes made (ie same style as the commit logs, see the commit list for examples).
The preferred style for code is, in most cases, GNU style, with tabs set to two white spaces, ie the same style as that which:
indent -nut
will format code to. For historical reasons, much of the code does not conform to this style, at least with respect to indentation. However, please try to minise whitespace changes in patches (see the -wb arguments to diff, as in the examples above).
If you submit a patch and do not receive a response, please try again. Mails can be missed, people can be busy. Ie it's best to consider email a lossy medium - implement your own delivery and flow control on top of it.
Various proposed patches to Quagga, which have not yet been integrated for whatever reason, are kept here. (listing of a patch in this directory does not neccessarily imply it will be integrated in that form).
