From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/7] OMFS filesystem version 3
Date: Mon, 14 Apr 2008 02:21:08 -0700
Message-ID: <20080414022108.92ce9b1d.akpm@linux-foundation.org>
References: <20080413080130.GA9622@infradead.org>
	<20080413012001.8d7967f4.akpm@linux-foundation.org>
	<20080413082815.GA20108@infradead.org>
	<E1JkzaV-0003Lm-NB@pomaz-ex.szeredi.hu>
	<1208121358.2700.4.camel@shinybook.infradead.org>
	<20080413154459.4b2f125d.akpm@linux-foundation.org>
	<20080413234920.63711ca7@core>
	<20080413161014.cb06964c.akpm@linux-foundation.org>
	<1208161859.3596.75.camel@skunk.anacadf.mentorg.com>
	<20080414014445.5b4a7b22.akpm@linux-foundation.org>
	<20080414090945.GA18494@infradead.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Xavier Bestel <xavier.bestel@free.fr>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	David Woodhouse <dwmw2@infradead.org>,
	Miklos Szeredi <miklos@szeredi.hu>, me@bobcopeland.com,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
To: Christoph Hellwig <hch@infradead.org>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from smtp1.linux-foundation.org ([140.211.169.13]:57135 "EHLO
	smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1750979AbYDNJWM (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Mon, 14 Apr 2008 05:22:12 -0400
In-Reply-To: <20080414090945.GA18494@infradead.org>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Mon, 14 Apr 2008 05:09:45 -0400 Christoph Hellwig <hch@infradead.org> wrote:

> the lastet crap code from the corporate drones.

That's about the fourth time you've made this assertion.  It is pointless,
it is of no use to anyone and it is unjustly insulting to a large number of
kernel developers.  Many of whom do a hell of a lot more kernel work than
you, I might add.

If you have issues with certain parts of the kernel code then tell us, with
a usable level of detail what they are.  Preferably as a reply-to-all prior
to that code being merged, but after merging is fine too.

Otherwise...