From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from opus.bloom.county (cpe-24-221-152-185.az.sprintbbd.net [24.221.152.185]) by dsl2.external.hp.com (Postfix) with ESMTP id BE071482A for ; Fri, 20 Apr 2001 09:54:18 -0600 (MDT) Date: Fri, 20 Apr 2001 08:51:48 -0700 From: Tom Rini To: "Eric S. Raymond" , Alan Cox , "Albert D. Cahalan" , Matthew Wilcox , james rich , linux-kernel@vger.kernel.org, parisc-linux@parisc-linux.org Subject: Re: [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention? Message-ID: <20010420085148.V13403@opus.bloom.county> References: <20010420101951.A6011@thyrsus.com> <20010420105934.A6668@thyrsus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20010420105934.A6668@thyrsus.com>; from esr@thyrsus.com on Fri, Apr 20, 2001 at 10:59:34AM -0400 List-ID: On Fri, Apr 20, 2001 at 10:59:34AM -0400, Eric S. Raymond wrote: > Alan Cox : > > > well, though. One is the kind I'm bumping into right now, where > > > somebody legitimately needs to make small (almost trivial) changes > > > scattered all through the tree. > > > > Yep. But such changes are rare. Or should be. > > Knowing that doesn't help me much, since I'm trying to fix up a global > namespace that touches everybody :-(. Which does boil down to having to work with trees other than Linus or Alans. Remember, the official tree is not always the up-to-date tree, or in the case of other arches, the most relevant tree. But if you send something off to a maintainer, there's a good chance (if they're still active) they'll do what you ask, and it'll get to Linus/Alan the next time they sync. As long as the problem gets fixed, it shouldn't be as important if it's fixed in everyones tree right now, or in a release or two. If it's some sort of huge bug it just might get fixed sooner. -- Tom Rini (TR1265) http://gate.crashing.org/~trini/