From: Bob Copeland <me@bobcopeland.com>
To: linux-wireless@vger.kernel.org
Subject: [ANNOUNCE] New location for wireless-testing tree
Date: Wed, 16 Dec 2015 12:32:23 -0500 [thread overview]
Message-ID: <20151216173223.GF4073@localhost> (raw)
As reported previously[1], John Linville will be moving on from maintenance
of the wireless-testing[2] tree at the end of the year. A huge thank you to
John for doing all this work for so many years!
We now have a shared wireless directory on kernel.org where we (currently
myself and Kalle as backup) will continue to maintain this tree going
forward. The new tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-testing.git
Note: unlike John's tree, we are going to try rebasing this tree on every
build (like linux-next) instead of merging the downstream trees, in order
to avoid certain merge problems when those trees are rebased.
This means that if you are working directly off of wireless-testing, use
'git pull --rebase' to sync, instead of just 'git pull'.
We'll see how this goes and reassess after a couple of cycles.
Please let me know of any issues.
[1] http://comments.gmane.org/gmane.linux.kernel.wireless.general/145291
[2] wireless-testing is an integration testing tree, consisting of:
* Linus's latest -rc
* patches in mac80211 and wireless-drivers (for the upcoming release)
* patches in mac80211-next and wireless-drivers-next (for the next release)
It is not pulled into any upstream tree, but it should be a pretty good
indication of what is baking in Linux wireless for the next release, without
having unrelated changes from all the other subsystems as in linux-next.
--
Bob Copeland %% http://bobcopeland.com/
next reply other threads:[~2015-12-16 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 17:32 Bob Copeland [this message]
2015-12-17 15:56 ` [ANNOUNCE] New location for wireless-testing tree John W. Linville
2015-12-17 17:41 ` Emmanuel Grumbach
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=20151216173223.GF4073@localhost \
--to=me@bobcopeland.com \
--cc=linux-wireless@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.