From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: anyone want to volunteer as 2.6 maintainer?
Date: Mon, 10 Nov 2003 17:50:36 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106848670128353@msgid-missing> (raw)
As the kernel is inching ever closer to the release of 2.6.0, I
thought it is time to start looking for someone to maintain the 2.6
tree. I'd expect the hand-off to happen as soon as 2.7.x opens up
(with me continuing to watch over the development kernel).
Could everyone interested in maintaining the stable 2.6 tree drop me a
note? Ideally, I'd like to find someone who has been around for a
while in ia64 linux land, is responsive, knows at least a little bit
about bitkeeper, etc. I can think of several potential candidates,
but I do have a very open mind on this and if you really think you
want to do this, by all means drop me a note.
--david
next reply other threads:[~2003-11-10 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 17:50 David Mosberger [this message]
2003-11-18 22:39 ` anyone want to volunteer as 2.6 maintainer? David Mosberger
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=marc-linux-ia64-106848670128353@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.