linux-kernel - About git-bisect (was: Linux 2.6.28-rc7)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <49356274.6080400@diamondcut.com.br>
Date:	Tue, 02 Dec 2008 14:29:40 -0200
From:	"Renato S. Yamane" <yamane@...mondcut.com.br>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: About git-bisect (was: Linux 2.6.28-rc7)

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/