From: Adrian Bunk <bunk@stusta.de>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@osdl.org>,
James Bottomley <James.Bottomley@SteelEye.com>,
linux-scsi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] SCSI aic7xxx: kill kernel 2.2 #ifdef's (fwd)
Date: Sat, 18 Dec 2004 03:06:35 +0100 [thread overview]
Message-ID: <20041218020635.GJ21288@stusta.de> (raw)
In-Reply-To: <41C23458.1080404@osdl.org>
On Thu, Dec 16, 2004 at 05:20:24PM -0800, Randy.Dunlap wrote:
> Alan Cox wrote:
> >>I would really appreciate it if you could limit patches for major
> >>subsystems to only the mailing list for those subsystems.
> >
> >
> >And then I'd have missed the lapb error for example. At least for less
> >maintained stuff do use this list
>
> netdev is _the_ mailing list for network-related development...
>
> scsi should happen on linux-scsi
>
> If we take your argument to an extreme, we only need
> one mailing list. :(
It does make sense:
If you are _only_ interested in SCSI related development, linux-scsi is
a good choice and a relatively low-volume list.
> ~Randy
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2004-12-18 2:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 22:18 [2.6 patch] SCSI aic7xxx: kill kernel 2.2 #ifdef's (fwd) Adrian Bunk
2004-12-16 23:04 ` Randy.Dunlap
2004-12-16 23:28 ` Alan Cox
2004-12-17 1:20 ` Randy.Dunlap
2004-12-18 2:06 ` Adrian Bunk [this message]
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=20041218020635.GJ21288@stusta.de \
--to=bunk@stusta.de \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rddunlap@osdl.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