From: <lmage11@twcny.rr.com>
To: Jesper Juhl <jj@chaosbits.net>, Kyle Moffett <kyle@moffetthome.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IRC?
Date: Mon, 29 Dec 2008 21:28:32 -0500 [thread overview]
Message-ID: <20081230022832.E1C7M.401856.root@hrndva-web19-z02> (raw)
In-Reply-To: <f73f7ab80812291823t2eb66f5dw900e854a8941ddf7@mail.gmail.com>
---- Kyle Moffett <kyle@moffetthome.net> wrote:
> On Mon, Dec 29, 2008 at 8:40 PM, Jesper Juhl <jj@chaosbits.net> wrote:
> > IRC channels can be a nice suplement when a few people need to discuss
> > something in semi-real-time related to some LKML thread or just some
> > kernel related topic, but it's no replacement for the mailing list.
>
> Especially considering that LKML can reach up to 60 lines per second
> for sustained periods of time during certain discussions, even
> excluding patch content. With subject filters and threading, that's
> perfectly OK. With a single big honkin' IRC channel it is beyond
> useless.
Aside from the fact that I'm not proposing a complete replacement, there
wouldn't have to be "a single big honkin' IRC channel" - as I said, there
could be a big general one for people who don't know exactly where to look
yet, and a bunch of smaller ones for each subsystem where the actual
discussion happens.
Ari
next prev parent reply other threads:[~2008-12-30 2:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 1:19 IRC? lmage11
2008-12-30 1:34 ` IRC? Russell Miller
2008-12-30 1:40 ` IRC? Jesper Juhl
2008-12-30 1:47 ` IRC? lmage11
2008-12-30 3:19 ` IRC? david
2008-12-30 2:23 ` IRC? Kyle Moffett
2008-12-30 2:28 ` lmage11 [this message]
2008-12-30 2:07 ` IRC? David Miller
2008-12-30 2:11 ` IRC? lmage11
2008-12-30 2:34 ` IRC? David Miller
2008-12-30 2:46 ` IRC? lmage11
2008-12-30 3:35 ` IRC? Kyle McMartin
2008-12-31 1:40 ` IRC? Christian Jaeger
2008-12-30 17:12 ` IRC? Stefan Richter
2008-12-31 14:01 ` IRC? 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=20081230022832.E1C7M.401856.root@hrndva-web19-z02 \
--to=lmage11@twcny.rr.com \
--cc=jj@chaosbits.net \
--cc=kyle@moffetthome.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®