From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: wireless-dev rebase (prep for -mm)
Date: Tue, 6 Feb 2007 20:08:10 -0500 [thread overview]
Message-ID: <20070207010810.GE23096@tuxdriver.com> (raw)
In case anyone doesn't know, wireless-dev is here:
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git
As I mentioned in London, I have kept this tree current w/ Linus by
pulling from his branch into the master merge branch. This has some
advantages for my immediate downstream driver maintainers, but it
has disadvantages. In particular, it makes it difficult to extract
a patch stream from wireless-dev that will directly apply on top of
a current tree from Linus, et al.
I have taken some time and applied some git foo so that now I have a
branch ("mm-master") that can yield such a patch stream. This branch
will be the base from which I will ask akpm to pull from -mm.
It is rooted on top of the "cfg80211" branch, which contains the
cfg80211 patches that I am grooming for an upstream merge in the
immediate future. For now, I will also continue to maintain the
"master" branch as I have done previously.
This message is intended to keep everyone who cares "in the loop".
Feel free to voice any concerns/complaints/suggestions.
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
reply other threads:[~2007-02-07 1:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070207010810.GE23096@tuxdriver.com \
--to=linville@tuxdriver.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 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).