From: Bob Copeland <me@bobcopeland.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Kalle Valo <kvalo@codeaurora.org>, linux-wireless@vger.kernel.org
Subject: Re: wireless-testing rebased, new HEAD commit f5feec4244464225c03ccc9ddad615cb43a044cc
Date: Tue, 8 Dec 2015 08:21:31 -0500 [thread overview]
Message-ID: <20151208132131.GA12251@localhost> (raw)
In-Reply-To: <20151207193910.GB27529@tuxdriver.com>
On Mon, Dec 07, 2015 at 02:39:11PM -0500, John W. Linville wrote:
> All,
>
> An earlier pull got a version of mac80211.git that was later reverted.
> Unfortunately, the intervening merges got things so screwed-up I
> couldn't reasonably unravel them. So, I have taken the somewhat
> unusual step of rebasing wireless-testing here in the middle of the
> 4.4 stream.
For this reason, we are considering making the new wireless-testing
rebase the feeder trees for each build instead of once per cycle,
similarly to how linux-next is built. For most users, the main
difference will behaving to remember to 'git pull --rebase' instead of
just 'git pull'.
If there are users that rely on the merging-type workflow, could you
weigh in on whether that is a strong requirement?
I'm running this in test-pilot mode now at its eventual home; comments
welcome:
https://git.kernel.org/cgit/linux/kernel/git/wireless/wireless-testing.git
--
Bob Copeland %% http://bobcopeland.com/
prev parent reply other threads:[~2015-12-08 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 6:54 wireless-testing regression: Could not configure driver mode Kalle Valo
2015-12-03 7:50 ` Johannes Berg
2015-12-03 17:40 ` John W. Linville
2015-12-07 19:39 ` wireless-testing rebased, new HEAD commit f5feec4244464225c03ccc9ddad615cb43a044cc John W. Linville
2015-12-08 13:21 ` Bob Copeland [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=20151208132131.GA12251@localhost \
--to=me@bobcopeland.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).