lkml.org 
[lkml]   [2013]   [Jul]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Stupid linux-next git question...
    Hi Valdis,

    On Wed, 31 Jul 2013 18:58:13 -0400 Valdis Kletnieks <Valdis.Kletnieks@vt.edu> wrote:
    >
    > OK... So I have (as usual) found some issues in linux-next, so I'm looking at 3
    > bisects. I already know that bisecting between (say) next-20130715 and
    > next-20130730 won't work, but bisecting between the 3.11-rc1 base of
    > next-20130715 and next-20130730 *will* work.
    >
    > Question 1:
    >
    > Does bisecting between "the HEAD of Linus's tree when a given next- is built"
    > and "some later next-" work? (basically, I know that anything in Linus's tree
    > as of -0715 is 'Good', so I'd rather start from there than from 3.11-rc1 to
    > save several bisects).

    Yes, because that point only moves forward (obviously).

    > Question 2:
    >
    > If that works, how do I determine the commit ID to feed to 'git bisect good'?
    > I *hope* this in Next/merge.log is the magic I'm looking for:
    >
    > $ git reset --hard stable
    > HEAD is now at 6c504ec Merge branch 'drm-fixes' of git://people.freedesktop.org/~airlied/linux
    > Merging origin/master (5ae90d8 Linux 3.11-rc3)

    Yes, that, or if you look in Next/SHA1s, my start point in Linus' tree is
    labelled "origin". Also, it is the "stable" branch in the current
    linux-next tree (which is moved forward each day).

    These are not stupid questions, by the way :-)
    --
    Cheers,
    Stephen Rothwell sfr@canb.auug.org.au
    [unhandled content-type:application/pgp-signature]
    \
     
     \ /
      Last update: 2013-08-01 02:21    [W:4.435 / U:0.024 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site