From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752671AbYDNJWW (ORCPT ); Mon, 14 Apr 2008 05:22:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751146AbYDNJWN (ORCPT ); Mon, 14 Apr 2008 05:22:13 -0400 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 ); Mon, 14 Apr 2008 05:22:12 -0400 Date: Mon, 14 Apr 2008 02:21:08 -0700 From: Andrew Morton To: Christoph Hellwig Cc: Xavier Bestel , Alan Cox , David Woodhouse , Miklos Szeredi , me@bobcopeland.com, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [PATCH 0/7] OMFS filesystem version 3 Message-Id: <20080414022108.92ce9b1d.akpm@linux-foundation.org> In-Reply-To: <20080414090945.GA18494@infradead.org> References: <20080413080130.GA9622@infradead.org> <20080413012001.8d7967f4.akpm@linux-foundation.org> <20080413082815.GA20108@infradead.org> <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> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.5; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 14 Apr 2008 05:09:45 -0400 Christoph Hellwig 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...