From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.105.134.102] (helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1DjWmR-00027I-OS for garchives@archives.gentoo.org; Sat, 18 Jun 2005 06:26:12 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j5I6PJ3p017088; Sat, 18 Jun 2005 06:25:19 GMT Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j5I6N8O7011646 for ; Sat, 18 Jun 2005 06:23:08 GMT Received: from [192.168.1.4] (pcp0011842295pcs.waldrf01.md.comcast.net[69.251.97.45]) by comcast.net (sccrmhc13) with ESMTP id <20050618062322016000o4tee>; Sat, 18 Jun 2005 06:23:23 +0000 Message-ID: <42B3BEAE.40608@gentoo.org> Date: Sat, 18 Jun 2005 02:26:54 -0400 From: Kumba User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] linux-2.6.12 References: <42B3A17D.6090306@leetworks.com> <200506180050.13233.vapier@gentoo.org> <42B3A8A7.9060508@leetworks.com> <20050617230517.0e976362@enterprise.weeve.org> <42B3B94E.70204@gentoo.org> <42B3B965.1030804@leetworks.com> In-Reply-To: <42B3B965.1030804@leetworks.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 7aaa719f-1367-4843-950b-b1053741f94d X-Archives-Hash: c656eb157ee4b9011daef21c1a8b4d23 Andrew Muraco wrote: > > > keep your wity comments to yourself -lol i dont think ext3 is going > anywhere for a long time.. I usually think this is why alot of people still rely on it. It's solid, and doesn't change very often, so people working in environments that require solid stability on Linux likely go with this. > reiserfs4 will merely be an option for > those of us that like post-proscessed organic material.. Just remember, bugs in vanilla-sources go here: http://bugzilla.kernel.org/ Any other -sources buggers up, try a variant of vanilla-sources to see if the problem exists there. If it does fire the bug upstream to the mainline kernel devs. If not, might be a patch we added in. I'm just stating this, because once reiserfs4 goes mainline (I believe it's in -mm currently), we are bound to have users hitting various bumps and ruts in the road using it, and if they file bugs to our bugzilla that aren't related to patches we produce, then they'll likely wind up closed as invalid and such. This saves the users time, and may get them the answers they seek (or at least a resolution of some kind). It also saves our bug-wranglers time by now having to deal with more invalid bugs. --Kumba -- Gentoo/MIPS Team Lead Gentoo Foundation Board of Trustees "Such is oft the course of deeds that move the wheels of the world: small hands do them because they must, while the eyes of the great are elsewhere." --Elrond -- gentoo-dev@gentoo.org mailing list