 |
 |
Articles / TULARC / PC info / Amiga / AmigaUUCP / |  |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
   |
|
||
|
1.3) Bug / Enhancement Reports |
|
||
|
||||
|
|
|
||
|
||||
|
|
|
|
||
|
||
|
|
|
|
||
|
|
||
|
||
|
|
|
|
||
|
||
This article is from the AmigaUUCP
FAQ, by Marc SCHAEFER,
[Note that the following text author is considered to be the current UUCP source maintainer which seems to be Michael B. Smith, mbs@adastra.cvl.va.us]
The alt.sys.amiga.uucp and alt.sys.amiga.uucp.patches groups are fed through a filter when they reach my machine, and any bug or enhancement reports of a specific format will be automatically extracted and appended to my TODO file.
To issue a bug report or enhancement request, use the following format:
##B unique-id
<bug report goes here>
##
Note that there are TWO '#'s. ##B stands for a bug report, ##E stands for an enhancement request. WARNING! The ##'s must begin a line, you CANNOT PRECEDE ## WITH WHITESPACE. Doing so will result in the filter passing the report by. For example, the ##B/## lines in the example above, not being flush with the left margin, will be ignored by my filter program.
The unique-id should be a unique identifier for your bug report, for example, I might use '##B dillon.23'. Do NOT encode the date in the unique ID because my filter program will automatically extract the Date: and From: fields from the news message header. Matt Dillon will use the ID when refering to previous bug reports rather than posting the whole bug report.
Continue to:
|
|
|
|
 |
|