aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2006-12-08 17:28:31 +0000
committerEli Zaretskii <eliz@gnu.org>2006-12-08 17:28:31 +0000
commit81e0e9408d050a8bcd7b36d6c969f5bdacfd0fd9 (patch)
tree0730968ac81624f9623addb9382417c6af78ae96
parent038224f6186b569d849c7416159bde789749094a (diff)
downloadgdb-81e0e9408d050a8bcd7b36d6c969f5bdacfd0fd9.zip
gdb-81e0e9408d050a8bcd7b36d6c969f5bdacfd0fd9.tar.gz
gdb-81e0e9408d050a8bcd7b36d6c969f5bdacfd0fd9.tar.bz2
Clarify the meaning of an ``obvious fix'' in the docs.
-rw-r--r--gdb/MAINTAINERS3
1 files changed, 3 insertions, 0 deletions
diff --git a/gdb/MAINTAINERS b/gdb/MAINTAINERS
index 8411454..64cc06c 100644
--- a/gdb/MAINTAINERS
+++ b/gdb/MAINTAINERS
@@ -95,6 +95,9 @@ Something like changing or bypassing an interface is _not_ an obvious
fix, since such a change without discussion will result in
instantaneous and loud complaints.
+For documentation changes, about the only kind of fix that is obvious
+is correction of a typo or bad English usage.
+
GDB Steering Committee
----------------------