![]() | ||||||||||
Messages in this thread |
On January 29, 2002 10:55 am, Matthias Andree wrote: > On Mon, 28 Jan 2002, Rob Landley wrote: > > > The holder of the patch penguin would feed Linus good patches, by Linus's > > standards. Not just tested ones, but small bite-sized patches, one per email > > as plain text includes, with an explanation of what each patch does at the > > top of the mail. (Just the way Linus likes them. :) Current pending patches > > from the patch penguin tree could even be kept at a public place (like > > kernel.org) so Linus could pull rather than push, and grab them when he has > > time. The patch penguin tree would make sure that when Linus is ready for a > > patch, the patch is ready for Linus. > > Looks like a manual re-implementation of a bug/request/patch tracker > like sourceforge's, bugzilla or whatever, with some additions. And you load a patch into it by emailing to the bot, not via the web interface. The web interface is just for a) reporting b) maintainance, i.e., closing out a patch that got applied in some altered form, or applied with no notification to the bot, or obsoleted. > A patch > is added to the system, it gets a version tag, and you just pull it, and > mark it closed if applied to Linus' tree. If Linus releases a new tree, > the patch is marked stale until the maintainer uploads an updated patch > or just reopens it to mark "still applies unchanged to new version". (No > CVS involved, BTW.) Yes, very much yes. This way it just looks like regular email to Linus - except for some hopefully useful bookkeeping gack prepended to the top of the mail by the bot - and doesn't change the way he works at all. -- Daniel - 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: 2005-03-22 11:15 [from the cache] ©2003-2008 | ||||||||||