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,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC 5/7] Docs: Expectations for bug reporters and maintainers
Date: Sat, 20 Apr 2013 01:24:53 -0500 [thread overview]
Message-ID: <1366439093.18069.122@driftwood> (raw)
In-Reply-To: <20130418235245.GA3565@xanatos> (from sarah.a.sharp@linux.intel.com on Thu Apr 18 18:52:45 2013)
On 04/18/2013 06:52:45 PM, Sarah Sharp wrote:
> Any other feedback on this patchset? If not, are you going to send
> it to Linus for 3.10 or should I?
Go for it, I still need to pitch a new tent on kernel.org now that I've
got my login back. (Touch overscheduled the past couple months...)
Meanwhile I've just been forwarding patches to the trivial tree when
they fall through the cracks.
> Sarah Sharp
Rob
next prev parent reply other threads:[~2013-04-21 1:48 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 [this message]
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=1366439093.18069.122@driftwood \
--to=rob@landley.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=torvalds@linux-foundation.org \
/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