From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2 of 8] manual: contributing: add section on analyzing bug reports
Date: Wed, 05 Mar 2014 17:24:28 +0100 [thread overview]
Message-ID: <0cc2a6824f249999fa57.1394036668@argentina> (raw)
In-Reply-To: <patchbomb.1394036666@argentina>
This patch adds a small section to the manual promoting the reproduction,
analysis and fixing of bug reports.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
docs/manual/contribute.txt | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt
--- a/docs/manual/contribute.txt
+++ b/docs/manual/contribute.txt
@@ -23,6 +23,16 @@ source code tarball. Git is the easiest
send your patches to the mailing list. Refer to xref:getting-buildroot[]
for more information on obtaining a Buildroot git tree.
+Reproducing, analyzing and fixing bugs
+--------------------------------------
+
+A first way of contributing is to have a look at the open bug reports in
+the https://bugs.busybox.net/buglist.cgi?product=buildroot[Buildroot bug
+tracker]. As we strive to keep the bug count as small as possible, all
+help in reproducing, analyzing and fixing reported bugs is more than
+welcome. Don't hesitate to add a comment to bug reports reporting your
+findings, even if you don't yet see the full picture.
+
[[submitting-patches]]
Submitting patches
------------------
next prev parent reply other threads:[~2014-03-05 16:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 16:24 [Buildroot] [PATCH 0 of 8] manual: rework Contributing chapter Thomas De Schampheleire
2014-03-05 16:24 ` [Buildroot] [PATCH 1 of 8] manual: contributing: expand introduction Thomas De Schampheleire
2014-03-05 17:11 ` Yann E. MORIN
2014-03-05 20:50 ` Samuel Martin
2014-03-05 16:24 ` Thomas De Schampheleire [this message]
2014-03-05 17:37 ` [Buildroot] [PATCH 2 of 8] manual: contributing: add section on analyzing bug reports Yann E. MORIN
2014-03-05 20:51 ` Samuel Martin
2014-03-05 16:24 ` [Buildroot] [PATCH 3 of 8] manual: contributing: move and expand autobuild section Thomas De Schampheleire
2014-03-05 17:48 ` Yann E. MORIN
2014-03-05 16:24 ` [Buildroot] [PATCH 4 of 8] manual: contributing: move section on patch reviews up and change intro Thomas De Schampheleire
2014-03-05 17:41 ` Yann E. MORIN
2014-03-05 20:57 ` Samuel Martin
2014-03-06 6:33 ` Arnout Vandecappelle
2014-03-05 16:24 ` [Buildroot] [PATCH 5 of 8] manual: contributing: add section on TODO list Thomas De Schampheleire
2014-03-05 17:17 ` Yann E. MORIN
2014-03-05 16:24 ` [Buildroot] [PATCH 6 of 8] manual: contributing: minor rewording of 'submitting patches' section Thomas De Schampheleire
2014-03-05 17:26 ` Yann E. MORIN
2014-03-06 6:39 ` Arnout Vandecappelle
2014-03-05 17:29 ` Yann E. MORIN
2014-03-05 20:59 ` Samuel Martin
2014-03-05 16:24 ` [Buildroot] [PATCH 7 of 8] manual: contributing: don't recommend leaving out changelog from patches Thomas De Schampheleire
2014-03-05 17:22 ` Yann E. MORIN
2014-03-05 16:24 ` [Buildroot] [PATCH 8 of 8] manual: contributing: minor rewording of 'reporting bugs' section Thomas De Schampheleire
2014-03-05 17:45 ` Yann E. MORIN
2014-03-05 21:05 ` Samuel Martin
2014-03-06 8:55 ` Thomas De Schampheleire
2014-03-06 9:21 ` Samuel Martin
2014-03-05 18:45 ` [Buildroot] [PATCH 0 of 8] manual: rework Contributing chapter Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0cc2a6824f249999fa57.1394036668@argentina \
--to=patrickdepinguin@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox