linux-kernel - Re: current git kernel has strange problems during bisect

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]

Date:	Sun, 11 Jan 2009 21:51:21 +0100 (CET)
From:	Johannes Schindelin <Johannes.Schindelin@....de>
To:	Andi Kleen <andi@...stfloor.org>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Christian Borntraeger <borntraeger@...ibm.com>,
	git@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: current git kernel has strange problems during bisect

Hi,

On Sun, 11 Jan 2009, Andi Kleen wrote:

> Linus Torvalds <torvalds@...ux-foundation.org> writes:
> >
> > For bisect purposes, if you know you're not chasing down a btrfs issue, 
> > you can do
> >
> > 	git bisect good 34353029534a08e41cfb8be647d734b9ce9ebff8
> 
> Could you perhaps add some standard tag for that commit? That 
> would make it easier than to always find the exact btrfs commit.
> 
> Just an idea.

Well, AFAICT what Linus hinted at is that you do not need such a standard 
tag.  Indeed, you would only clutter the history with such tags, when it 
usually is just a matter of saying "git bisect good" whenever you _know_ 
you are hitting known-good history.

Ciao,
Dscho

--
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/