Re: [Bug #12422] 2.6.28-git can't resume from str

Ingo Molnar
2009-01-11T18:07:14Z

* Jeff Chua <jeff.chua.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> On Mon, Jan 12, 2009 at 12:39 AM, Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org> wrote:
> > * Christian Borntraeger <borntraeger-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org> wrote
> >> I guess Jeff, meant the other way around.
> >> Since a0e280e0f33f6c859a235fb69a875ed8f3420388 is a fix for a known S2R
> >> problem , the earlier patch (before) does of course not work.
> > ah, okay.
> > So i suspect that at every bisection point, this should be done:
> > git cherry-pick a0e280e0f33f6c859a235fb69a875ed8f3420388
>
> I started with the latest git, and did this ...
>
> git bisect start
> git bisect bad
> git bisect good a0e280e0f33f6c859a235fb69a875ed8f3420388
>
> Everything in-between should have
> a0e280e0f33f6c859a235fb69a875ed8f3420388 applied?

not necessarily - if an intermediate tree that is checked happened to have
been based on some earlier -rc, it might have that bug included. Safest is
to always cherry-pick that commit. (if it has no dependencies)

Ingo