* snapshots.readme: Clarify when obvious and non-obvious bugs

	should be reported.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 57a368d9f6319f95a37199c4217eeb4f83eae864..d22891df0ff38cfb5130d9a1f2212bc23c93d9f3 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@
+Mon May 24 11:09:06 1993  Fred Fish  (fnf@cygnus.com)
+
+       * snapshots.readme:  Clarify when obvious and non-obvious bugs
+       should be reported.
+
 Mon May 24 09:00:33 1993  Jim Kingdon  (kingdon@lioth.cygnus.com)
 
        * stabs.texinfo (Stabs Format):  Misc fixes.

diff --git a/gdb/doc/snapshots.readme b/gdb/doc/snapshots.readme
index 49dca83698ca6897d9996f0ab25c8d23ed51eef0..17c74ad5f3d69373e72cc8ee8a239257d66e2249 100644 (file)
--- a/gdb/doc/snapshots.readme
+++ b/gdb/doc/snapshots.readme
@@ -1,6 +1,6 @@
                         GDB SNAPSHOT SYSTEM
                            (general info)
-                           Updated 5/7/93
+                           Updated 5/24/93
 
 WHAT ARE GDB SNAPSHOTS
 ----------------------
@@ -149,6 +149,24 @@ gnu.gdb.bug).  Nobody there will have any idea what you are talking about
 and it will just cause confusion.
 
 
+BUG REPORTS
+-----------
+
+Send bug reports to gdb-patches@cygnus.com.
+
+Note that since no testing is done on the snapshots, and snapshots may even
+be made when gdb is in an inconsistent state, it may not be unusual for an
+occasional snapshot to have a very obvious bug, such as failure to compile
+on *any* machine.  It is likely that such bugs will be fixed by the next
+snapshot, so it really isn't necessary to report them unless they persist
+for a couple days.
+
+Bugs which are non-obvious, such as failure to compile on only a specific
+machine, a new machine dependent bug (particularly one not detected by the
+testsuite), missing machine dependent files, etc should be reported when
+you discover them, or have a suggested patch to fix them.
+
+
 FORMAT FOR PATCHES
 ------------------