From: Kalle Valo <kvalo@codeaurora.org>
To: Bob Copeland <me@bobcopeland.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Arend van Spriel <arend@broadcom.com>,
Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>
Subject: Re: wireless-testing repo
Date: Wed, 25 Nov 2015 11:22:56 +0200 [thread overview]
Message-ID: <87a8q2ph5b.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20151123164640.GA4037@localhost> (Bob Copeland's message of "Mon, 23 Nov 2015 11:46:40 -0500")
Bob Copeland <me@bobcopeland.com> writes:
> On Mon, Nov 23, 2015 at 11:02:00AM -0500, John W. Linville wrote:
>> > We have some setups running on wl-testing kernel and some running distro
>> > kernel using backports.
>>
>> I believe the Bob Copeland is considering taking on this mantle...
>
> "a" Bob Copeland :)
>
> Yeah, I would be game for maintaining this for a while -- I've scripted
> a bit of it and have a practice tree over here, although of course it
> should be on kernel.org when for reals:
>
> https://github.com/bcopeland/wireless-testing-testing
>
> But if maintenance becomes a burden there's no reason we couldn't spread
> the load.
I think it would be a good idea to have a shared "wireless" directory
for the wireless-testing, similarly like linux-firmware.git has. That
way the location doesn't change if the maintainer changes or if we have
more than one maintainer.
And I can act as a backup for Bob whenever he is too busy or offline.
--
Kalle Valo
next prev parent reply other threads:[~2015-11-25 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 11:19 wireless-testing repo Arend van Spriel
2015-11-23 11:31 ` Johannes Berg
2015-11-23 11:38 ` Arend van Spriel
2015-11-23 16:02 ` John W. Linville
2015-11-23 16:46 ` Bob Copeland
2015-11-25 9:22 ` Kalle Valo [this message]
2015-11-25 12:25 ` Bob Copeland
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=87a8q2ph5b.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arend@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=me@bobcopeland.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;
as well as URLs for NNTP newsgroup(s).