From: Joe Perches <joe@perches.com>
To: Simon Arlott <simon@fire.lp0.eu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [133/2many] MAINTAINERS - CONEXANT ACCESSRUNNER USB DRIVER
Date: Mon, 13 Aug 2007 11:43:34 -0700 [thread overview]
Message-ID: <1187030615.10249.247.camel@localhost> (raw)
In-Reply-To: <46C09DA6.3020700@simon.arlott.org.uk>
On Mon, 2007-08-13 at 19:06 +0100, Simon Arlott wrote:
> NAK: Strange patch title "[133/2many] ...."
I didn't expect these patches to be accepted as is actually.
There isn't _that_ much difference between sending a 200KB
patch file and what I sent. Nail could use the ability to
add a threading header though.
next prev parent reply other threads:[~2007-08-13 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:25 [PATCH] [133/2many] MAINTAINERS - CONEXANT ACCESSRUNNER USB DRIVER joe
2007-08-13 18:06 ` Simon Arlott
2007-08-13 18:43 ` Joe Perches [this message]
2007-08-13 19:23 ` Jan Engelhardt
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=1187030615.10249.247.camel@localhost \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@fire.lp0.eu \
/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