From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "Mukker, Atul" <Atulm@lsil.com>,
bunk@fs.tum.de, sreenib@lsil.com, Manojj@lsil.com,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [patch] 2.6.9-rc1-mm1: megaraid_mbox.c compile error with gcc 3.4
Date: 29 Aug 2004 09:34:22 -0400 [thread overview]
Message-ID: <1093742635.1670.5.camel@mulgrave> (raw)
In-Reply-To: <20040828130419.57a56cdd.akpm@osdl.org>
On Sat, 2004-08-28 at 16:04, Andrew Morton wrote:
> I dunno about James, but I *really* dislike receiving patches by going and
> getting them from internet servers. It breaks our commonly-used tools. It
> loses authorship info. It loses Signed-off-by: info. There is no
> changelog. All this means that your patch is more likely to be ignored by
> busy people. Please, just email the diffs.
Yes, I dislike it, but I've learned to live with downloading...
The Megaraid patch set, by the way, annoys me even more by not actually
applying to the kernel tree. it doesn't reflect the fact that the
Changelog.megaraid is under Documentation/scsi not drivers/scsi.
However, it's all merged into the vanilla kernel now but in future, if
you could follow Andrew's guide, I'd be very grateful.
James
next prev parent reply other threads:[~2004-08-29 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 16:29 [patch] 2.6.9-rc1-mm1: megaraid_mbox.c compile error with gcc 3.4 Mukker, Atul
2004-08-28 20:04 ` Andrew Morton
2004-08-28 20:17 ` Lee Revell
2004-08-29 13:34 ` James Bottomley [this message]
2004-08-31 6:49 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2004-08-30 13:05 Mukker, Atul
2004-08-30 19:55 ` Andrew Morton
2004-08-26 8:47 2.6.9-rc1-mm1 Andrew Morton
2004-08-28 9:06 ` [patch] 2.6.9-rc1-mm1: megaraid_mbox.c compile error with gcc 3.4 Adrian Bunk
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=1093742635.1670.5.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Atulm@lsil.com \
--cc=Manojj@lsil.com \
--cc=akpm@osdl.org \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sreenib@lsil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox