From: Luca Santini <luca.santini@spesonline.com>
To: linux-sh@vger.kernel.org
Subject: Re: git pull breaks edosk7760 kernel
Date: Sun, 23 Nov 2008 15:06:18 +0000 [thread overview]
Message-ID: <4929716A.6030207@spesonline.com> (raw)
In-Reply-To: <4927F204.5090805@spesonline.com>
Thanks Matt,
i tried to use git-bisect, and i hope i used it fine; this is my final output:
406f9e9cfe5d44fbcdc6e8f4b1f205e1160c0fef is first bad commit
commit 406f9e9cfe5d44fbcdc6e8f4b1f205e1160c0fef
Author: Paul Mundt <lethal@linux-sh.org>
Date: Tue Nov 18 14:22:39 2008 +0900
sh: __udivdi3 -> do_div() in softfloat lib.
Inhibit the generation of __udivdi3 for the softfloat lib, use do_div()
outright.
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
:040000 040000 70142433e2ab902b50182ea127ea1e56803dac87 7801a0a6ef1e2d6703f82fa82587ba03fe140048 M arch
...and now?
Matt Fleming wrote:
> On Sat, Nov 22, 2008 at 12:50:28PM +0100, Luca Santini wrote:
>> Hi all,
>> yesterday i pulled from git and obtained an unbootable kernel.
>> My last working pull is dated
>>
>> commit 882b689432129bfe77530d61f70797147179a742
>> Merge: b86c2c0... fb059cd...
>> Author: Luca Santini <santox@libero.it>
>> Date: Thu Nov 13 11:31:54 2008 +0100
>>
>>
>> The only thing i was able to do is git reset --hard HEAD^
>>
>> i'm not a god of git... is there a way to "pull step by step" and find the
>> offending patch(es)? --
>
> The usual way to find the commit that introduced a bug is via git-bisect.
>
> Checkout http://www.kernel.org/doc/local/git-quick.html#bisect
>
>
next prev parent reply other threads:[~2008-11-23 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 11:50 git pull breaks edosk7760 kernel Luca Santini
2008-11-22 12:35 ` Matt Fleming
2008-11-23 15:06 ` Luca Santini [this message]
2008-11-24 3:37 ` Paul Mundt
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=4929716A.6030207@spesonline.com \
--to=luca.santini@spesonline.com \
--cc=linux-sh@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 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.