diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 1996-12-10 16:19:57 +0000 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 1996-12-10 16:19:57 +0000 |
| commit | 58698de7f70f6cf2e2fb1193900d36bf68878153 (patch) | |
| tree | 7a416b68d31264c3b17cb54f0f9d3ec8493c0edd | |
| parent | 09a10331be1b5565d827b9c8eb0024c548b8265a (diff) | |
| download | fetchmail-58698de7f70f6cf2e2fb1193900d36bf68878153.tar.gz fetchmail-58698de7f70f6cf2e2fb1193900d36bf68878153.tar.bz2 fetchmail-58698de7f70f6cf2e2fb1193900d36bf68878153.zip | |
Move the bug-reporting advice FAQ.
svn path=/trunk/; revision=622
| -rw-r--r-- | INSTALL | 18 |
1 files changed, 1 insertions, 17 deletions
@@ -100,23 +100,7 @@ fetchmail core dumps (especially near startup) try recompiling without 6. REPORTING BUGS -You should read the FAQ file before rfeporting a bug. - -When reporting bugs, please include the following: - -1. Your operating system and compiler version. -2. The release and patch level of the fetchmail you are running. You can see - your patchlevel by typing `fetchmail -V'. -3. The output of fetchmail -V (this will not reveal your password). -4. Any command-line options you used. - -It is helpful if you include your .fetchmailrc, but not necessary -unless your symptom seems to involve an error in configuration parsing. - -A transcript of the failed session with -v on is almost always useful. -If the bug involves a core dump, a gdb stack trace is good to have. - -Best of all is a mail file which, when fetched, will reproduce the bug. +You should read the FAQ file before reporting a bug. 7. USE IT |