From: "John W. Linville" <linville@tuxdriver.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: ethtool needs a new maintainer
Date: Thu, 30 Jun 2016 14:15:06 -0400 [thread overview]
Message-ID: <20160630181505.GB2778@tuxdriver.com> (raw)
In-Reply-To: <20160627135146.GB6864@tuxdriver.com>
On Mon, Jun 27, 2016 at 09:51:47AM -0400, John W. Linville wrote:
> On Sun, Jun 26, 2016 at 06:11:41PM +0200, Ben Hutchings wrote:
> > I've become steadily less enthusiastic and less responsive as a
> > maintainer over the past year or so. I no longer work on networking
> > regularly, so it takes a lot more time to get into the right state of
> > mind to think about ethtool code, while I have other demands on my time
> > that tend to take priority.
> >
> > So, I would like to find a new maintainer to take over as soon as
> > possible. Ideally the new maintainer would have previous contributions
> > to ethtool and an existing account on kernel.org so that they can push
> > to the git repository and the home page. But neither of those is
> > essential. Please reply if you're interested.
>
> I would like to take this responsibility. My previous contributions
> to ethtool are meager, but I think my skills and interests are suited
> to the task. Plus, I already have a kernel.org account... :-)
Are there any other takers? Or is this a done deal?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2016-06-30 18:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 15:59 ethtool 4.6 released Ben Hutchings
2016-06-26 16:11 ` ethtool needs a new maintainer Ben Hutchings
2016-06-27 13:51 ` John W. Linville
2016-06-30 18:15 ` John W. Linville [this message]
2016-06-30 19:27 ` Jorge Alberto Garcia
2016-06-30 19:32 ` Ben Hutchings
[not found] ` <CAPfrtUce=xzHystAoMRth4HEKhZtSj629f07R-t-dsq5=9q0-g@mail.gmail.com>
[not found] ` <CAPfrtUeQuKiHAejZmhYORUh+1ZrD0QnAJ4PszRi++O-+dindoA@mail.gmail.com>
[not found] ` <CAPfrtUeYwu8hj_ZNvp97_=v1hFuNBNPTG+Rfct644aTRh=JBog@mail.gmail.com>
2016-06-30 21:51 ` John W. Linville
2016-07-04 17:38 ` Ben Hutchings
2016-06-30 22:12 ` John Fastabend
2016-07-01 18:31 ` Andy Gospodarek
2016-07-01 19:33 ` David Miller
[not found] ` <CAD=hENfD=cwAidNe1+kspzUtUzwk3QqQE8GWF7zdhrKogPt-=A@mail.gmail.com>
2016-07-04 18:00 ` Ben Hutchings
2016-07-04 14:24 ` Jiri Pirko
2016-07-04 17:18 ` Ben Hutchings
2016-07-05 15:58 ` John W. Linville
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=20160630181505.GB2778@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ben@decadent.org.uk \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).