From: Eric Raymond <esr@thyrsus.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] branching the kernel, etc.
Date: Tue, 8 Feb 2011 12:59:52 -0500 [thread overview]
Message-ID: <20110208175952.GC7744@thyrsus.com> (raw)
In-Reply-To: <20110208163022.GE2448@tuxdriver.com>
John W. Linville <linville@tuxdriver.com>:
> > Branching the kernel, and maintaining it, seems to be a major
> > headache. I'd like someone with cred in the kernel communities to step
> > up, when it's needed. That person is not me. Anyone?
>
> I can do this. FWIW, I am the Linux kernel maintainer for wireless
> LANs already. I'm already good at handling patches I don't fully
> understand... :-)
>
> Any objections?
Objections? Not hardly...I think we love you! :-)
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
prev parent reply other threads:[~2011-02-08 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 18:09 Dave Täht
2011-02-06 21:01 ` Dan McDonald
2011-02-08 16:30 ` [Bloat] " John W. Linville
2011-02-08 17:59 ` Eric Raymond [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=20110208175952.GC7744@thyrsus.com \
--to=esr@thyrsus.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=linville@tuxdriver.com \
/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