Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261576AbVAMLGY (ORCPT ); Thu, 13 Jan 2005 06:06:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261599AbVAMLDm (ORCPT ); Thu, 13 Jan 2005 06:03:42 -0500 Received: from smartmx-02.inode.at ([213.229.60.34]:63654 "EHLO smartmx-02.inode.at") by vger.kernel.org with ESMTP id S261576AbVAMKwd (ORCPT ); Thu, 13 Jan 2005 05:52:33 -0500 Subject: Re: [fuse-devel] Merging? From: Bernhard Schauer Reply-To: schauer@acousta.at To: Miklos Szeredi , lkml In-Reply-To: References: Content-Type: text/plain Date: Thu, 13 Jan 2005 11:52:02 +0100 Message-Id: <1105613522.6178.9.camel@FC3-bernhard-1.acousta.local> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 839 Lines: 21 > Well, there doesn't seem to be a great rush to include FUSE in the > kernel. Maybe they just don't realize what they are missing out on ;) I'm a little bit confused... a few weeks ago I read a thread regarding the remove of some - unneeded ? - symbols from IEEE1394 core. Some persons in the discussion told, that everything should be included into kernel mainline, cause if not, symbols needed may be removed. Now here is the discussion about including FUSE into kernel... So WHAT? In any case, I do not think that FUSE, compiled in as module, could bother someone. regards Bernhard - 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/