* Kernel bisect: a query regarding commit identifiers
@ 2010-07-21 11:29 trapDoor
2010-07-21 11:45 ` trapDoor
0 siblings, 1 reply; 3+ messages in thread
From: trapDoor @ 2010-07-21 11:29 UTC (permalink / raw)
To: LKML
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
?
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Kernel bisect: a query regarding commit identifiers
2010-07-21 11:29 Kernel bisect: a query regarding commit identifiers trapDoor
@ 2010-07-21 11:45 ` trapDoor
2010-07-22 3:31 ` Randy Dunlap
0 siblings, 1 reply; 3+ messages in thread
From: trapDoor @ 2010-07-21 11:45 UTC (permalink / raw)
To: LKML
On Wed, Jul 21, 2010 at 12:29 PM, trapDoor <trapdoor6@gmail.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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Kernel bisect: a query regarding commit identifiers
2010-07-21 11:45 ` trapDoor
@ 2010-07-22 3:31 ` Randy Dunlap
0 siblings, 0 replies; 3+ messages in thread
From: Randy Dunlap @ 2010-07-22 3:31 UTC (permalink / raw)
To: trapdoor6; +Cc: LKML
On Wed, 21 Jul 2010 12:45:53 +0100 trapDoor wrote:
> On Wed, Jul 21, 2010 at 12:29 PM, trapDoor <trapdoor6@gmail.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 ..
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 ***
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-07-22 3:31 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-07-21 11:29 Kernel bisect: a query regarding commit identifiers trapDoor
2010-07-21 11:45 ` trapDoor
2010-07-22 3:31 ` Randy Dunlap
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.