lkml.org 
[lkml]   [2008]   [Jun]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Diagnosing linux-next (Was: Re: m68k libc5 regression)
    On Sun, 1 Jun 2008 23:26:38 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:

    > Hi Andrew,
    >
    > On Sun, 1 Jun 2008 00:53:38 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
    > >
    > > I do not know how to work out how this patch got into linux-next.
    >
    > I have been wondering for a while what I can do to make figuring this out
    > (in general) easier. Would adding the SHA1 of the head of each tree to
    > the Trees file help? I could publish all the branches in my linux-next
    > repo - but they change daily. I guess only the git users benefit from
    > those suggestions.
    >
    > gitk can tell you pretty easily (just find the offending commit and work
    > your way upward until you find a merge by me).
    >

    hm, I just found the `committer' line in gitk. Coulda sworn that
    wasn't there yesterday.


    \
     
     \ /
      Last update: 2008-06-01 23:07    [W:2.358 / U:0.780 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site