From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Confused - bisecting wireless-testing
Date: Tue, 27 Jul 2010 12:04:34 -0400 [thread overview]
Message-ID: <20100727160434.GB31694@tuxdriver.com> (raw)
In-Reply-To: <AANLkTimS2d0jZnu-44+cbFQXvitj_3Rq3egttgOzEiRh@mail.gmail.com>
On Tue, Jul 27, 2010 at 08:56:54AM -0700, Luis R. Rodriguez wrote:
> On Tue, Jul 27, 2010 at 7:01 AM, John W. Linville
> <linville@tuxdriver.com> wrote:
> > On Mon, Jul 26, 2010 at 08:27:06PM -0700, Luis R. Rodriguez wrote:
> >> 04:23 * mcgrof is confused, I just did a git bisect -i on
> >> wireless-testing on some patch on Fri Jul 2 00:09:49 2010 and ended
> >> up with a 2.6.34 top level
> >> Makefile
> >> 04:23 < mcgrof> it was git rebase -i ba17bc5e55ba541d2a8765fca53b6883b667ab21
> >> 04:23 < mcgrof> eh
> >> 04:24 < mcgrof> how am I supposed to bisect wl now
> >> 04:24 < mcgrof> the odd thing though is that the top commit is ancient
> >> 04:24 < mcgrof> http://paste.pocoo.org/show/242077/
> >> 04:24 < mcgrof> but the other ones are OK
> >>
> >> I realize we should use wireless-2.6.git to bisect stable but I need
> >> to bisect against recent patches that spans different master- tags
> >> from you, I figured git bisecting wireless-testing would work now that
> >> you are using a different method to move your tree forward but am I
> >> wrong? Should I only bisect between master tags still?
> >
> > wireless-testing is a nasty mess when it comes to bisection.
> > I am considering a one-time rebase of wireless-testing after the
> > next -rc1, now that the current process is working reasonably well.
> > wireless-testing will continue to have a messy history, but it should
> > be a bit less nasty after a rebase.
> >
> > As for right now, it sounds like you should just use wireless-next-2.6
> > instead?
>
> Oh OK, didn't realize that was bisectable, thanks. Also was unsure if
> I'd get other subsystems's -next components. Is wireless-next.git just
> the -next bits for 802.11 or does it also suck up net-next?
Usually just the wireless bits, but I did just pull the bluetooth stuff
(which included some net-next stuff).
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-07-27 16:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 3:27 Confused - bisecting wireless-testing Luis R. Rodriguez
2010-07-27 3:30 ` Luis R. Rodriguez
2010-07-27 14:01 ` John W. Linville
2010-07-27 15:56 ` Luis R. Rodriguez
2010-07-27 16:04 ` John W. Linville [this message]
2010-07-27 16:21 ` Luis R. Rodriguez
2010-07-27 16:31 ` John W. Linville
2010-07-27 16:54 ` Luis R. Rodriguez
2010-07-27 17:18 ` John W. Linville
2010-07-27 17:36 ` Luis R. Rodriguez
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=20100727160434.GB31694@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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.