From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Next Month/Changes to where to send stuff
Date: 20 Aug 2003 13:05:10 +0100 [thread overview]
Message-ID: <1061381109.32752.23.camel@dhcp23.swansea.linux.org.uk> (raw)
At the end of September I'm off back to University on a years sabbatical
from Red Hat to study for an MBA. I've made the decision that I'm
basically going to vanish for the year so I can concentrate on the
course, and on the pet side project of learning Welsh.
I've passed all my userspace projects on to other people already, and
I'll be vanishing from kernel space too (except to a few priviledged
processes ;)). Lots of people send me stuff as a gateway to getting it
into 2.4 and 2.6. Lots of people send me security related stuff.
Can you in future please send stuff to
Security: vendor-sec@lst.de
2.4: Marcelo/the list/someone he nominates to do that job
2.6: Andrew Morton or for small stuff Rusty Russell's trivial patch
manager.
The 2.2 tree needs a new maintainer, someone who can spend their entire
life refusing patches, being ignored by the mainstream (because 2.2 is
boring) and by vendors (who don't ship 2.2 any more).
I'm not sure what to do about the -ac patch. Most of the remaining stuff
is "pending Marcelo" for 2.4 mainstream, but not the O(1) scheduler and
some of the odder cool stuff (like the morse bits). As 2.6 becomes
relevant 2.4-ac basically becomes a fixed collection of add-ons that
aren't mainstream anyway. And of course there are other people keeping
patch sets in the same way nowdays.
A few years ago I'd have worried about doing this, the great thing is
that with the kernel community we have today I know I'm not a critical
cog in the machine. In fact I'm surrounded by people far better than I
am and we even have Andrew Morton to keep Linus in check 8)
Dal ati!
Alan
next reply other threads:[~2003-08-20 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 12:05 Alan Cox [this message]
2003-08-21 4:51 ` Aschwin Marsman
-- strict thread matches above, loose matches on Subject: below --
2003-08-20 11:46 PATCH: Maintainer/Credit update Alan Cox
2003-08-20 11:59 ` Marc-Christian Petersen
2003-08-21 10:30 ` Next Month/Changes to where to send stuff Marc-Christian Petersen
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=1061381109.32752.23.camel@dhcp23.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--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®