summaryrefslogtreecommitdiffstats
path: root/CONTRIBUTING.d/bugs
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-15 19:41:07 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-15 19:41:07 +0000
commit3af6d22bb3850ab2bac67287e3a3d3b0e32868e5 (patch)
tree3ee7a3ec64525911fa865bb984c86d997d855527 /CONTRIBUTING.d/bugs
parentAdding debian version 6.05.01-1. (diff)
downloadmanpages-3af6d22bb3850ab2bac67287e3a3d3b0e32868e5.tar.xz
manpages-3af6d22bb3850ab2bac67287e3a3d3b0e32868e5.zip
Merging upstream version 6.7.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'CONTRIBUTING.d/bugs')
-rw-r--r--CONTRIBUTING.d/bugs28
1 files changed, 28 insertions, 0 deletions
diff --git a/CONTRIBUTING.d/bugs b/CONTRIBUTING.d/bugs
new file mode 100644
index 0000000..4b8cf74
--- /dev/null
+++ b/CONTRIBUTING.d/bugs
@@ -0,0 +1,28 @@
+Name
+ Bugs - instructions for reporting bugs
+
+Description
+ Report bugs to the mailing list. If you can write a patch, it's
+ very welcome.
+
+ If you're unsure if the bug is in the manual page or in the code
+ being documented (kernel, glibc, ...), it's best to send the
+ report to both at the same time, that is, CC all the mailing
+ lists that may be concerned by the report.
+
+ Some distributions (for example Debian) apply patches to the
+ upstream manual pages. If you suspect the bug is in one of those
+ patches, report it to your distribution maintainer.
+
+ Send logically separate reports. For unrelated pages, or for
+ logically-separate issues in the same page, send separate emails.
+
+ There's also a bugzilla, but we don't use it as much as the
+ mailing list. If you want to track your bug there, feel free to
+ open a bug report, but expect more attention in the mailing list.
+
+See also
+ CONTRIBUTING
+ CONTRIBUTING.d/*
+
+ <https://bugzilla.kernel.org/buglist.cgi?component=man-pages>