Contents|Index|Previous|Next

Filling out a problem report

Problem reports are structured so that a database program can manage them. When you fill out the form, please remember the following guidelines.

- Each pr needs a valid customer-id and category.
- Describe only one problem per pr.
- For follow-up mail, use the same subject line as the one in the automatic acknowledgment. It shows the category, the pr number and the original synopsis line. This causes your mail to automatically be filed with the original bug report. Your follow-up comments will be sent to all the people who are working on the bug.
- Please try to make the subject or synopsis line as informative as possible. For misbehaving software, you might use a sentence of the form Encrypted rlogin hangs if you send interrupt or g++: calling wrong overloaded function.
- You dont need to delete the comment lines while editing the pr form; this is done by send-pr. Put your information before or after the comments.

See An Example and other related discussions in Reporting Problems in GNUPro Advanced Topics for more discussion on this topic.