From: "Renato S. Yamane" <yamane@diamondcut.com.br>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: About git-bisect (was: Linux 2.6.28-rc7)
Date: Tue, 02 Dec 2008 14:29:40 -0200 [thread overview]
Message-ID: <49356274.6080400@diamondcut.com.br> (raw)
In-Reply-To: <alpine.LFD.2.00.0812020804590.3256@nehalem.linux-foundation.org>
Linus Torvalds wrote:
> Just do
>
> git bisect start
> git bisect bad v2.6.27
> git bisect good v2.6.28-rc6-00007-ged31348
>
> and off you go. That would help enormously.
Hi Linus, is possible plan something to make faster and easier the way
to loking for a specific bug?
E.g:
<https://bugs.launchpad.net/ubuntu/+source/linux/+bug/110784>
In this bug, I think that it appear after ~2.6.22, so is necessary do a
git-bisect more than 13 times!
I need more than 20min to compile each kernel, so is necessary ~260min.
My wife will kill me if I says: Hey baby, wait 260min to me compile a
lot of kernel here.
Best regards,
Renato
next prev parent reply other threads:[~2008-12-02 16:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 4:11 Linux 2.6.28-rc7 Linus Torvalds
2008-12-02 12:14 ` Alejandro Riveira Fernández
2008-12-02 13:11 ` pazke
2008-12-02 14:48 ` Alejandro Riveira Fernández
2008-12-02 15:20 ` Alistair John Strachan
2008-12-02 15:50 ` Alejandro Riveira Fernández
2008-12-02 16:14 ` Alistair John Strachan
2008-12-02 15:54 ` Alejandro Riveira Fernández
2008-12-02 15:50 ` Linus Torvalds
2008-12-02 15:56 ` Alejandro Riveira Fernández
2008-12-02 16:13 ` Linus Torvalds
2008-12-02 16:29 ` Renato S. Yamane [this message]
2008-12-02 16:55 ` About git-bisect (was: Linux 2.6.28-rc7) Sam Ravnborg
2008-12-02 17:05 ` Linus Torvalds
2008-12-02 17:01 ` Linus Torvalds
2008-12-02 18:49 ` Linux 2.6.28-rc7 Alejandro Riveira Fernández
2008-12-02 19:22 ` Alejandro Riveira Fernández
2008-12-02 19:23 ` Linus Torvalds
2008-12-02 19:45 ` Alejandro Riveira Fernández
2008-12-02 20:40 ` Linus Torvalds
2008-12-02 20:29 ` Al Viro
-- strict thread matches above, loose matches on Subject: below --
2008-12-02 16:55 About git-bisect (was: Linux 2.6.28-rc7) Toralf Förster
[not found] <bEuTZ-3Ya-5@gated-at.bofh.it>
[not found] ` <bECot-57C-1@gated-at.bofh.it>
[not found] ` <bEFPF-XO-15@gated-at.bofh.it>
[not found] ` <bEFPG-XO-19@gated-at.bofh.it>
[not found] ` <bEG8P-1xl-15@gated-at.bofh.it>
[not found] ` <bEGiz-1Hw-11@gated-at.bofh.it>
[not found] ` <bEGLI-2aS-31@gated-at.bofh.it>
[not found] ` <bEGVc-2Bk-11@gated-at.bofh.it>
2008-12-02 21:52 ` Francis Moreau
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=49356274.6080400@diamondcut.com.br \
--to=yamane@diamondcut.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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