From: Andrew Morton <akpm@linux-foundation.org>
To: mcs6502@gmail.com
Cc: linux-kernel@vger.kernel.org, Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [patch 00/31] pci_ids.h, kernel 2.6.27-rc1, sort DEVICE_IDs within VENDOR_IDs
Date: Wed, 30 Jul 2008 03:42:55 -0700 [thread overview]
Message-ID: <20080730034255.ac5aa6c2.akpm@linux-foundation.org> (raw)
In-Reply-To: <E1KO7OU-0007BT-Ff@wraith.cs.uow.edu.au>
On Wed, 30 Jul 2008 18:50:50 +1000 mcs6502@gmail.com wrote:
> From: mcs6502@gmail.com
> To: unlisted-recipients:;;@imap1.linux-foundation.org (no To-header on input)
Something went wrong with the From: and To: lines.
Jesse wasn't cc'ed?
> Subject: [patch 00/31] pci_ids.h, kernel 2.6.27-rc1, sort DEVICE_IDs within VENDOR_IDs
a) the patch title shouldn't include the kernel version - that
information becomes instantly irrelevant (and soon wrong) as soon as
someone merges the patch.
It is sometimes useful to include this information, but it should
be inside [], so the patch recipient can automatically remove it.
(otoh, the patch _should_ be against latest Linus mainline, so
it's not very useful info).
b) all 31 patches had the same title. This causes numerous
problems. Please think up unique and relevant titles for each
patch.
> Date: Wed, 30 Jul 2008 18:50:50 +1000
> Sender: linux-kernel-owner@vger.kernel.org
>
> The following 31 patches attempt to bring pci_ids.h back into order.
This patchset will be utterly ghastly for someone to maintain for two
months. The PCI and linux-next trees will be worst hit.
So we either
a) slam it into mainline immediately or
b) ask you to regenerate it during the 2.6.28 merge window or
c) forget the whole idea.
next prev parent reply other threads:[~2008-07-30 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 8:50 [patch 00/31] pci_ids.h, kernel 2.6.27-rc1, sort DEVICE_IDs within VENDOR_IDs mcs6502
2008-07-30 10:42 ` Andrew Morton [this message]
2008-07-30 10:35 ` Alan Cox
2008-07-30 14:23 ` Jesse Barnes
2008-07-30 15:10 ` Arjan van de Ven
2008-07-30 15:41 ` Jesse Barnes
2008-07-30 12:13 ` Theodore Tso
2008-07-30 13:54 ` David Wilson
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=20080730034255.ac5aa6c2.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcs6502@gmail.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