linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 24 Sep 2010 16:05:33 -0400	[thread overview]
Message-ID: <20100924200532.GH8077@tuxdriver.com> (raw)
In-Reply-To: <4C9CFD86.2080207@candelatech.com>

On Fri, Sep 24, 2010 at 12:35:34PM -0700, Ben Greear wrote:
> Is there a rebased version of wireless-testing, or is there a way to
> tell git to not apply any patch that was later reverted when pulling?
> 
> I'd like to pull wireless-testing changes into a tree based on linux-2.6,
> but I want it clean enough to easily see what changes I actually
> pulled in.
> 
> If not, I can manually pull in some patches as needed.

Don't do that -- wireless-testing is and likely always will be a mess.
It really only exists as a "-next lite" for those that only want
bleeding-edge wireless while keeping-up with linux-2.6 release
candidates.

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.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2010-09-24 20: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 [this message]
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
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=20100924200532.GH8077@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).