From: Rob Landley <rob@landley.net>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [RFC 4/7] Docs: Add info on supported kernels to REPORTING-BUGS.
Date: Tue, 16 Apr 2013 19:24:13 -0500 [thread overview]
Message-ID: <1366158253.18069.109@driftwood> (raw)
In-Reply-To: <2c97a63f6fec91db91241981808d099ec60a4688.1366046390.git.sarah.a.sharp@linux.intel.com> (from sarah.a.sharp@linux.intel.com on Mon Apr 15 12:33:33 2013)
On 04/15/2013 12:33:33 PM, Sarah Sharp wrote:
> One of the most common frustrations maintainers have with bug
> reporters
> is the email that starts with "I have a two year old kernel from an
> embedded vendor with some random drivers and fixes thrown in, and it's
> crashing".
>
> Be specific about what kernel versions the upstream maintainers will
> fix
> bugs in, and direct bug reporters to their Linux distribution or
> embedded vendor if the bug is in an unsupported kernel.
Back in 2006 I wrote a section of the BusyBox FAQ about this:
http://git.busybox.net/busybox/tree/docs/busybox.net/FAQ.html?id=95718b3091690f1293e3069da75d0d4be2665d0e#n359
(Alas, the current version of that page had a large project specific
chunk dumped into the middle of it, but the text I linked to out of the
repo is reasonably generic to just about any project. Feel free to lift
anything that's useful. :)
Rob
next prev parent reply other threads:[~2013-04-17 0:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 17:33 [RFC 0/7] Update REPORTING-BUGS Sarah Sharp
2013-04-15 17:33 ` [RFC 1/7] Trivial: docs: Remove six-space indentation in REPORTING-BUGS Sarah Sharp
2013-04-15 17:33 ` [RFC 2/7] Docs: Step-by-step directions for reporting bugs Sarah Sharp
2013-04-15 17:33 ` [RFC 3/7] Docs: Add "Gather info" section to REPORTING-BUGS Sarah Sharp
2013-04-15 17:33 ` [RFC 4/7] Docs: Add info on supported kernels " Sarah Sharp
2013-04-17 0:24 ` Rob Landley [this message]
2013-04-15 17:33 ` [RFC 5/7] Docs: Expectations for bug reporters and maintainers Sarah Sharp
2013-04-17 2:15 ` Rob Landley
2013-04-17 18:23 ` Sarah Sharp
2013-04-17 23:49 ` Rob Landley
2013-04-18 23:52 ` Sarah Sharp
2013-04-20 6:24 ` Rob Landley
2013-04-19 6:08 ` Greg KH
2013-05-01 15:26 ` Mark Brown
2013-04-15 17:33 ` [RFC 6/7] Docs: Add a tips section to REPORTING-BUGS Sarah Sharp
2013-04-15 17:33 ` [RFC 7/7] Docs: Move ref to Frohwalt Egerer to end of REPORTING-BUGS Sarah Sharp
2013-04-15 21:40 ` [RFC 0/7] Update REPORTING-BUGS Linus Torvalds
2013-04-16 1:47 ` Theodore Ts'o
2013-04-16 21:58 ` Sarah Sharp
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=1366158253.18069.109@driftwood \
--to=rob@landley.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.