From a99a027138e0919a5221083a3d45c288bcce5359 Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Thu, 17 Apr 1997 08:06:04 +0000 Subject: Bug caveat. svn path=/trunk/; revision=964 --- fetchmail-FAQ.html | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index 7de91de1..f4dd655c 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -9,7 +9,7 @@

Frequently Asked Questions About Fetchmail

-$Id: fetchmail-FAQ.html,v 1.4 1997/04/17 07:56:59 esr Exp $

+$Id: fetchmail-FAQ.html,v 1.5 1997/04/17 08:06:04 esr Exp $

(Added C6 on working with qmail and C7 on managing fetchmail in the presence of @@ -144,7 +144,16 @@ If the bug involves a core dump or hang, a gdb stack trace is good to have. (Bear in mind that you can attach gdb to a running but hung process by giving the process ID as a second argument.)

-Best of all is a mail file which, when fetched, will reproduce the bug.

+Best of all is a mail file which, when fetched, will reproduce the +bug.

+ +Any bug I can reproduce will usually get fixed very quickly, often +within 48 hours. Bugs I can't reproduce are a crapshoot. If the +solution isn't obvious when I first look, it may evade me for a long +time (or to put it another way, fetchmail is well enough tested that the +easy bugs have long since been found). So if you want your bug fixed +rapidly, it is not just sufficient but nearly necessary that +you give me a way to reproduce it.

G4. I have this idea for a neat feature. Will you add it?

-- cgit v1.2.3