From: Christian Neumair <christian-neumair@web.de>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Separate 2.4 and 2.5 lkml?
Date: 23 Jul 2002 12:06:24 +0200 [thread overview]
Message-ID: <1027418785.5210.12.camel@kellerbar.lan.net> (raw)
In-Reply-To: <200207231159.10934.roy@karlsbakk.net>
Am Die, 2002-07-23 um 11.59 schrieb Roy Sigurd Karlsbakk:
> hi all
>
> How would it be to separate the 2.4 and 2.5 (or just stable and devel) lists?
> I'm currently one of those most interested in 2.4, as I don't do much kernel
> hacking.
This isn't a good idea as there are many issues affecting both kernel
series and some people looking for support wouldn't even know where to
ask their questions.
In Addition, some right issues (e.g. copyright violations) are discussed
here not regarding kernel development directly.
If you want a more compact overview just have a look at kernel
traffic[1]
see you,
Chris
[1]: http://kt.linuxcare.com/kernel-traffic/index.epl
prev parent reply other threads:[~2002-07-23 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 9:59 Roy Sigurd Karlsbakk
2002-07-23 10:06 ` Christian Neumair [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=1027418785.5210.12.camel@kellerbar.lan.net \
--to=christian-neumair@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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®