From: Ben Greear <greearb@candelatech.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: rebased version of wireless-testing?
Date: Sat, 25 Sep 2010 08:59:25 -0700 [thread overview]
Message-ID: <4C9E1C5D.4020805@candelatech.com> (raw)
In-Reply-To: <20100925134325.GD1948@tuxdriver.com>
On 09/25/2010 06:43 AM, John W. Linville wrote:
> On Fri, Sep 24, 2010 at 02:14:30PM -0700, Ben Greear wrote:
>
>>> You will be better-off pulling wireless-next-2.6 (and maybe
>>> wireless-2.6 as well). The history there isn't always immutable
>>> (although I prefer it to be), but it will tend to be a lot cleaner
>>> than wireless-testing.
>>
>> Any chance you could push tags in wireless-next-2.6?
>
> Not sure what you mean -- are you not seeing the master-<date> tags?
It didn't seem like the 2.6.36-rcX tags were there..but then again, maybe
I'm looking for something that doesn't exist?
Basically, my goal is to pull in most or all of the changes from wireless-testing
into a tree based on Linus's tree (2.6.36-rc5 currently). But, I need to keep
my tree clean enough to deal with rebasing and following Linus's tree because I have
a bunch of my own patches to add as well.
If nothing else, I'll manually pull the virtual-wifi patches that I need out of wireless-testing
and apply them to my tree.
Thanks,
Ben
>
> John
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-09-25 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 19:35 rebased version of wireless-testing? Ben Greear
2010-09-24 20:05 ` John W. Linville
2010-09-24 21:14 ` Ben Greear
2010-09-25 13:43 ` John W. Linville
2010-09-25 15:59 ` Ben Greear [this message]
2010-09-27 15:02 ` John W. Linville
2010-09-27 15:57 ` Ben Greear
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=4C9E1C5D.4020805@candelatech.com \
--to=greearb@candelatech.com \
--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 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.