[lkml]   [2007]   [Mar]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: 2.6.21-rc1: known regressions (part 2)

    * Linus Torvalds <> wrote:

    > But most likely, 9f4bd5dd is actually already bad, and what you are
    > seeing is two *different* bugs that just have the same symptoms
    > ("suspend doesn't work").

    the situation is simpler than that: there is a /known/ bug, and i marked
    the bugfix commit as 'good'. I never met such a multiple-bugs scenario
    before and forgot that git-bisect could easily pick a tree without this
    essential bugfix and would not be able to make a distinction between the
    two types of badness.

    I'll try what i've described in the previous mail: mark all bisection
    points that do not include f3ccb06f as 'good' - thus 'merging' the
    known-bad area with the first known-good commit, and thus eliminating it
    from the bisection space.

    (but it might also be useful to have a "git-bisect must-include" kind of
    command that would allow this to be automated: mark a particular tree as
    an essential component of the search space.)

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-03-02 08:31    [W:0.020 / U:41.512 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site