[lkml]   [2006]   [Aug]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH][RFC] exception processing in early boot
On Wed, Aug 30, 2006 at 02:59:14PM +0200, Andi Kleen wrote:
> > Unfortunately, this situation is even more difficult for me, because it's
> > getting very hard to track patches that get applied, rejected, modified or
> > obsoleted, which is even more true when people don't always think about
> > sending an ACK after the patch finally gets in. I already have a few pending
> > patches in my queue waiting for an ACK that will have to be tracked if the
> > persons do not respond, say, within one week. Otherwise I might simply lose
> > them.
> It shouldn't be that hard to check gitweb or git output occasionally
> for the patches. You can probably even automate that.

That's already what I'm doing, and yes, it is *that* hard. We're literally
speaking about *thousands* of patches. It's as difficult to find one patch
within 2.6 git changes as it is to find a useful mail in the middle of 99%
spam. This is not because of GIT but because of the number of changes.

> > I think that the good method would be to :
> > - announce the patch
> > - find a volunteer to port it
> > - apply it once the volunteer agrees to handle it
> > This way, no code gets lost because there's always someone to track it.
> I can put that one into my tree for .19

Thanks for this andi,

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: 2006-08-30 15:19    [W:0.079 / U:14.980 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site