From: "John W. Linville" <linville@tuxdriver.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: rebased version of wireless-testing?
Date: Mon, 27 Sep 2010 11:02:35 -0400 [thread overview]
Message-ID: <20100927150235.GB11086@tuxdriver.com> (raw)
In-Reply-To: <4C9E1C5D.4020805@candelatech.com>
On Sat, Sep 25, 2010 at 08:59:25AM -0700, Ben Greear wrote:
> 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?
Ah...well, they probably won't be in there until after 2.6.36 is
released. I generally don't pull from Linus into that tree during
the release cycle in order to avoid surprising Dave when he pulls it.
But if you are basing on linux-2.6 then you should already have those
tags anyway?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-09-27 15:14 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
2010-09-27 15:02 ` John W. Linville [this message]
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=20100927150235.GB11086@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=greearb@candelatech.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).