On Fri, Mar 7, 2014 at 2:48 AM, Paul Bolle <pebolle@xxxxxxxxxx> wrote:
> Bjorn Helgaas schreef op ma 10-02-2014 om 14:33 [-0700]:
>> I wouldn't start bisecting yet, but if you're in the mood, this
>> commit: 96702be56037 "Merge branch 'pci/resource' into next" looks
>> like a good place to start, so you could try the pre-merge commit:
>> 04f982beb900 "Merge branch 'pci/msi' into next". If 04f982beb900 is
>> good, there are only about 15 commits on the pci/resource branch to
>> look at.
>
> This might end up not being relevant. And this is surely documented
> somewhere, but anyhow:
> - what git magic returns the hashes of the 15 commits that merge commit
> 96702be56037 added to the tree; and
"git show 96702be56037" gives:
commit 96702be560374ee7e7139a34cab03554129abbb4
Merge: 04f982beb900 d56dbf5bab8c
...
04f982beb900 is the previous HEAD, d56dbf5bab8c is the head of the
branch merged by this commit. "git log 04f982beb900..96702be56037"
shows the commits merged.
> - how can I use the list of those hashes to limit the range of commits
> to do a git bisect?
I'm not a git bisect expert, but I *think* you should be able to do
something like this:
git bisect start
git bisect bad 96702be56037
git bisect good 04f982beb900
(assuming you've verified that 96702be56037 really *is* bad and
04f982beb900 really *is* good), and git should checkout something in
the middle and you can build and test it, then use "git bisect good"
or "git bisect bad" depending on the result.
Bjorn
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
