Re: Kernel bisect: a query regarding commit identifiers

[Randy Dunlap]

On Wed, 21 Jul 2010 12:45:53 +0100 trapDoor wrote:

> On Wed, Jul 21, 2010 at 12:29 PM, trapDoor <trapdoor6@xxxxxxxxx> 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 ..

git snapshot IDs are stored at http://kernel.org/pub/linux/kernel/v2.6/snapshots/ ,
in the *.id files.  E.g.:

patch-2.6.35-rc5-git7.id contains:
cd5b8f8755a89a57fc8c408d284b8b613f090345

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/