Before reporting a bug, see if it is a known one in the bugs file. Send all bug reports to amd-dev@majordomo.cs.columbia.edu quoting the details of the release and your configuration. These can be obtained by running the command `amd -v'. It would greatly help if you could provide a reproducible procedure for detecting the bug you are reporting.

Providing working patches is highly encouraged. Every patch incorporated, however small, will get its author an honorable mention in the authors file.

[ < ]

[ > ]

[ << ]

[ Up ]

[ >> ]

[Top]

[Contents]

[Index]

[ ? ]

Mailing List

There are two mailing lists for people interested in keeping up-to-date with developments.

The older list, `amd-workers' is for general "how to" questions and announcements. To subscribe, send a note to amd-workers-request@majordomo.glue.umd.edu.(1) To post a message to this list, send mail to amd-workers@majordomo.glue.umd.edu.
The developers only list, `amd-dev' is for
- announcements of alpha and beta releases of am-utils
- reporting of bugs and patches
- discussions of new features for am-utils
- implementation and porting issues
To subscribe, send a note to majordomo@majordomo.cs.columbia.edu with the single body text line `subscribe amd-dev'. To post a message to this list, send mail to amd-dev@majordomo.cs.columbia.edu. To avoid as much spam as possible, only subscribers to this list may post to it.
Subscribers of `amd-dev' are most suitable if they have the time and resources to test new and buggy versions of amd, on as many different platforms as possible. They should also be prepared to learn and use the GNU Autoconf, Automake, and Libtool packages, and of course, be very familiar with the complex code in the am-utils package. In other words, subscribers on this list should be able to contribute meaningfully to the development of amd.