![]() | |||||||||||||
Messages in this thread |
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, Willy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-08-30 13:19 [from the cache] ©2003-2008 | |||||||||||||