lkml.org 
[lkml]   [2008]   [May]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: git trees which are not yet in linux-next
Andrew Morton wrote:
> On Fri, 2 May 2008 15:12:06 -0700
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
>> The first
>> problem is working out "how the heck did that patch get into linux-next"?
>> That would be much easier if the signoff trail was complete for git-based
>> patches, but it often is not.
>
> doh. I'm pulling linux-next's constituent trees independently, so if I
> spot a turd in linux-next I can just grep the various git trees to find out
> where it came from.
>
> It seems wrong though...

What about the committer info? Well, I suppose a nobody@localhost slips
in, but more often I expect it to be something more telling than that.
--
Stefan Richter
-=====-==--- -=-= ---==
http://arcgraph.de/sr/


\
 
 \ /
  Last update: 2008-05-03 03:23    [W:0.089 / U:0.336 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site