mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [RFC 7/7] Docs: Move ref to Frohwalt Egerer to end of REPORTING-BUGS
Date: Mon, 15 Apr 2013 10:33:36 -0700	[thread overview]
Message-ID: <8d874c1030e1ae4c174d8f947841ee3ee196f898.1366046390.git.sarah.a.sharp@linux.intel.com> (raw)
In-Reply-To: <cover.1366046390.git.sarah.a.sharp@linux.intel.com>

The document is largely not the same as the original that was crafted
from Frohwalt Egerer's document, but leave it in as a historical thank
you footnote.

Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
---
 REPORTING-BUGS |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/REPORTING-BUGS b/REPORTING-BUGS
index d397e918..0cb8cdf 100644
--- a/REPORTING-BUGS
+++ b/REPORTING-BUGS
@@ -77,7 +77,6 @@ threads or separate bugzilla entries.  If you report several unrelated
 bugs at once, it's difficult for maintainers to tease apart the relevant
 data.
 
-[Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]
 
 Gather information
 ------------------
@@ -171,3 +170,5 @@ responding to these types of bugs in a timely manner (especially during a
 merge window), escalate the bug to LKML and Linus Torvalds.
 
 Thank you!
+
+[Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]
-- 
1.7.9


  parent reply	other threads:[~2013-04-15 17:34 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
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 ` Sarah Sharp [this message]
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=8d874c1030e1ae4c174d8f947841ee3ee196f898.1366046390.git.sarah.a.sharp@linux.intel.com \
    --to=sarah.a.sharp@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.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

all inboxes | Powered by JetHome®