linux-kernel - Re: Kernel bisect: a query regarding commit identifiers

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: <AANLkTinnlq27qoTicG-_C26N6Sv8pP8taEkXWF5BUE1b@mail.gmail.com>
Date:	Wed, 21 Jul 2010 12:45:53 +0100
From:	trapDoor <trapdoor6@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Kernel bisect: a query regarding commit identifiers

On Wed, Jul 21, 2010 at 12:29 PM, trapDoor <trapdoor6@...il.com> wrote:
> Hello All,
> Just a quick question. I'm going to do kernel bisect and was wondering
> if there are commit identifiers for the rc-GIT versions ? Or maybe I
> won't need it and could just do it like this:
> git-bisect bad 2.6.35-rc2-git3
> git-bisect good 2.6.35-rc2-git4
>
> ?

I meant the other way of course..
git-bisect bad 2.6.35-rc2-git4
git-bisect good 2.6.35-rc2-git3

>
> Identifiers for rc versions appear in changelogs but I can't find
> identifiers for the rc-git's. I think that doing bisect between rc-git
> version within the same rc would save me some time. Assuming I will be
> able to narrow a problem down to a particular rc initially ..


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