summaryrefslogtreecommitdiff
path: root/docs/contributing.txt
diff options
context:
space:
mode:
authorMark Whitley2001-03-27 21:20:05 +0000
committerMark Whitley2001-03-27 21:20:05 +0000
commit5b8939b1472d163c4bdd459554d0a6b329a06d97 (patch)
tree5982c0f2389c53272d165e6e3defa8da8433fc88 /docs/contributing.txt
parent9a2144663a97acb9c071c6d6e496d99a24d80685 (diff)
downloadbusybox-5b8939b1472d163c4bdd459554d0a6b329a06d97.zip
busybox-5b8939b1472d163c4bdd459554d0a6b329a06d97.tar.gz
Some more words on sending patches to the bug-tracker.
Diffstat (limited to 'docs/contributing.txt')
-rw-r--r--docs/contributing.txt15
1 files changed, 15 insertions, 0 deletions
diff --git a/docs/contributing.txt b/docs/contributing.txt
index cafa6ed..abfd516 100644
--- a/docs/contributing.txt
+++ b/docs/contributing.txt
@@ -332,6 +332,12 @@ Detailed instructions on how to submit a bug to the tracking system are at:
http://bugs.lineo.com/Reporting.html
+If you have a patch that will fix and close a reported bug, please send a
+message to [bugnumber]@bugs.lineo.com with your patch attached. It will catch
+people's attention if you have a subject line like the following:
+
+ [PATCH INCLUDED] - Fix attached, please apply and close this bug
+
Improving Your Chances of Patch Acceptance
@@ -392,6 +398,15 @@ place in the form of mailing lists, the bug tracking system, and CVS. Please
use these resources.
+Send Patches to the Bug Tracking System
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This was mentioned above in the "Making Sure Your Patch Doesn't Get Lost"
+section, but it is worth mentioning again. A patch sent to the mailing list
+might be unnoticed and forgotten. A patch sent to the bug tracking system will
+be stored and closely connected to the bug it fixes.
+
+
Be Polite
~~~~~~~~~