From: noer AT cygnus DOT com (Geoffrey Noer)
Subject: How to make gnu-win32 bug reports
11 Dec 1996 19:49:16 -0800
Sender: daemon AT cygnus DOT com
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <199612120125.RAA11432.cygnus.gnu-win32@cirdan.cygnus.com>
Content-Type: text
Original-To: gnu-win32 AT cygnus DOT com
Original-Cc: noer AT cygnus DOT com (Geoffrey Noer)
X-Mailer: ELM [version 2.4 PL23]
Content-Length: 1174      
Original-Sender: owner-gnu-win32 AT cygnus DOT com

When you report bugs to the gnu-win32 mailing list, *please* try
to follow these guidelines:

1) Use a subject line that describes the issue well:

Good examples:
	"pipe bug in b17.1"
	"problem building perl with b17.1"
	"question about catting binary files in bash"

Bad examples:
	"beta 17 bug"
	"porting problem"
	"bash question"

This also applies to general discussion.  It's very hard to follow
the list when most of the subject lines look very similar.

2) In your description, show how to reproduce the problem.  This means
including a test case if at all possible.

3) At the very least, always include which gnu-win32 beta release you are
using and give the operating system and its version number.  E.g.
"beta 17.1 under NT 4.0".

4) Keep in mind that there are over 1200 people on the mailing list.  Try
to avoid "me too" responses or reporting problems that have already been
reported.  It's hard enough keeping up with the volume as it is...

5) Include a patch to fix the problem if you can.  I'm going to
write and send another piece of mail soon that explains how to rebuild the
tools and send patches.

Thanks very much!

-- 
Geoffrey Noer
noer AT cygnus DOT com
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".