From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Kurt Garloff <garloff@suse.de>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Patch submissions
Date: Tue, 06 Mar 2001 16:29:20 -0500 [thread overview]
Message-ID: <3AA556B0.976557B0@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0103061542550.1409-100000@duckman.distro.conectiva>
Rik van Riel wrote:
> On Tue, 6 Mar 2001, Kurt Garloff wrote:
> > On Tue, Mar 06, 2001 at 02:22:58PM -0300, Rik van Riel wrote:
> > > probably even out of linux-kernel ...
> >
> > No. I want to see experimental stuff on l-k. That's what it's meant for.
>
> Putting the experimental stuff which isn't on l-k at the
> moment would probably triple the volume of this list, if
> not more ...
>
> I'm pretty sure most people already find l-k traffic too
> heavy to keep up. If you want to read all the experimental
> stuff of all the subsystems, why not subscribe to the
> mailing lists of those subsystems ?
Every patch doesn't need to go to lkml, but keeping linux-kernel folks
updated on experimental issues is always IMHO a good idea. Otherwise,
interested folks who don't have time to find out about and subscribe to
1000 other lists are kept informed.
Jeff
--
Jeff Garzik | "You see, in this world there's two kinds of
Building 1024 | people, my friend: Those with loaded guns
MandrakeSoft | and those who dig. You dig." --Blondie
next prev parent reply other threads:[~2001-03-06 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-06 16:56 Patch submissions Alan Cox
2001-03-06 17:02 ` Lars Marowsky-Bree
2001-03-06 17:23 ` Rik van Riel
2001-03-06 17:22 ` Rik van Riel
2001-03-06 18:26 ` Kurt Garloff
2001-03-06 18:44 ` Rik van Riel
2001-03-06 21:29 ` Jeff Garzik [this message]
2001-03-06 23:46 ` Andrew Morton
2001-03-07 0:54 ` Rik van Riel
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=3AA556B0.976557B0@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=garloff@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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