Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 27 Dec 2001 13:18:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 27 Dec 2001 13:18:52 -0500 Received: from vindaloo.ras.ucalgary.ca ([136.159.55.21]:15046 "EHLO vindaloo.ras.ucalgary.ca") by vger.kernel.org with ESMTP id ; Thu, 27 Dec 2001 13:17:36 -0500 Date: Thu, 27 Dec 2001 11:17:50 -0700 Message-Id: <200112271817.fBRIHov31985@vindaloo.ras.ucalgary.ca> From: Richard Gooch To: Dave Jones Cc: Russell King , Alan Cox , Rik van Riel , Dana Lacoste , "'Eyal Sohya'" , Subject: Re: The direction linux is taking In-Reply-To: In-Reply-To: <200112271804.fBRI41m31583@vindaloo.ras.ucalgary.ca> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Dave Jones writes: > On Thu, 27 Dec 2001, Richard Gooch wrote: > > > Sure, although I post to l-k a URL and ChangeLog, and separately send > > to Linus/Marcelo the actual patch. People grumble when I send kiB's > > (or even kB's :-) to the list. > > Good enough. (In fact, preferable imo, as long as the patch stays > at the url if still relevant/unapplied). Oh, sure. . I've still got a devfs patch dating back to 20-AUG-1998 on my ftp site. I think that's long enough :-) > The "I sent a patch n times to linus without ccing l-k and he didn't > apply it" case however, is a lost one imo. Agreed. Patches need review. It's actually quite frustrating when you post patches, wait a week, send it off to Linus/Marcelo, and when the new kernel comes out, suddenly bug reports come out of the woodwork. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca - 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/