From: Andrew Morton <akpm@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git-bisect problem
Date: Mon, 13 Feb 2006 16:56:20 -0800 [thread overview]
Message-ID: <20060213165620.11ec6051.akpm@osdl.org> (raw)
In-Reply-To: <7v8xsezsni.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
>
> Sorry, this question is what I do not quite understand.
>
> Here is my understanding of the situation.
>
> - Betweeen 2.6.16-rc1 and 2.6.16-rc2 a bug you are chasing was
> introduced. You know rc1 works fine but rc2 is bad.
>
> - You suspect that changes introduced by merging Jeff's tree
> at some point between -rc1 and -rc2 may be causing this.
>
> Am I totally misunderstanding the situation?
yup ;)
The bug is in Jeff's tree only
(git+ssh://master.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git#ALL)
so I wanted to perform the bisection on the git-netdev-all branch.
So I did a `git log git-netdev-all' and looked at where the ipw2200 changes
were and then decided that the 2.6.16-rc1 and 2.6.16-rc2 commits straddled
those changes nicely, so I chose those as the bisection starting points.
next prev parent reply other threads:[~2006-02-14 0:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 8:25 git-bisect problem Andrew Morton
2006-02-13 9:11 ` Junio C Hamano
2006-02-13 9:32 ` Andrew Morton
2006-02-13 9:39 ` Ryan Anderson
2006-02-13 9:51 ` Andrew Morton
2006-02-13 9:58 ` Fernando J. Pereda
2006-02-13 10:22 ` Luben Tuikov
2006-02-13 10:23 ` Luben Tuikov
2006-02-13 12:21 ` cat-file (was Re: git-bisect problem) Joshua N Pritikin
2006-02-13 10:14 ` git-bisect problem Ryan Anderson
2006-02-13 10:25 ` Andrew Morton
2006-02-13 16:44 ` Linus Torvalds
2006-02-13 10:40 ` Luben Tuikov
2006-02-13 10:44 ` Andrew Morton
2006-02-14 0:33 ` Junio C Hamano
2006-02-13 10:08 ` Junio C Hamano
2006-02-13 10:19 ` Andrew Morton
2006-02-14 0:32 ` Junio C Hamano
2006-02-14 0:56 ` Andrew Morton [this message]
2006-02-14 1:14 ` Linus Torvalds
2006-02-14 1:15 ` Petr Baudis
2006-02-14 1:27 ` Petr Baudis
2006-02-14 1:52 ` Junio C Hamano
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=20060213165620.11ec6051.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.