From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lazybastard.de ([212.112.238.170] helo=longford.logfs.org) by bombadil.infradead.org with esmtps (Exim 4.68 #1 (Red Hat Linux)) id 1JjEFD-0005a0-5c for linux-mtd@lists.infradead.org; Tue, 08 Apr 2008 13:52:16 +0000 Date: Tue, 8 Apr 2008 15:52:04 +0200 From: =?utf-8?B?SsO2cm4=?= Engel To: Arnd Bergmann Subject: Re: [patch 1/15] Makefiles and Kconfig Message-ID: <20080408135203.GB670@logfs.org> References: <20080401181308.512473173@logfs.org> <200804080230.17426.arnd@arndb.de> <20080408083316.GA31262@logfs.org> <200804081542.00333.arnd@arndb.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200804081542.00333.arnd@arndb.de> Cc: linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 8 April 2008 15:41:59 +0200, Arnd Bergmann wrote: > On Tuesday 08 April 2008, Jörn Engel wrote: > > "Logfs file system" might make sense.  LOGFS_FS is something I would > > rather avoid.  For some reason my brain reacts strongly to repetition, > > redundancy and superfluous information. > > > > How about LOG_FS then? I don't think there is a really good argument > either way, but a large majority uses the *_FS notation in Kconfig. Fair enough. Jörn -- Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface. -- Doug MacIlroy From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753737AbYDHNwX (ORCPT ); Tue, 8 Apr 2008 09:52:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751985AbYDHNwN (ORCPT ); Tue, 8 Apr 2008 09:52:13 -0400 Received: from lazybastard.de ([212.112.238.170]:52184 "EHLO longford.logfs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751736AbYDHNwN (ORCPT ); Tue, 8 Apr 2008 09:52:13 -0400 Date: Tue, 8 Apr 2008 15:52:04 +0200 From: =?utf-8?B?SsO2cm4=?= Engel To: Arnd Bergmann Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org Subject: Re: [patch 1/15] Makefiles and Kconfig Message-ID: <20080408135203.GB670@logfs.org> References: <20080401181308.512473173@logfs.org> <200804080230.17426.arnd@arndb.de> <20080408083316.GA31262@logfs.org> <200804081542.00333.arnd@arndb.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200804081542.00333.arnd@arndb.de> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 8 April 2008 15:41:59 +0200, Arnd Bergmann wrote: > On Tuesday 08 April 2008, Jörn Engel wrote: > > "Logfs file system" might make sense.  LOGFS_FS is something I would > > rather avoid.  For some reason my brain reacts strongly to repetition, > > redundancy and superfluous information. > > > > How about LOG_FS then? I don't think there is a really good argument > either way, but a large majority uses the *_FS notation in Kconfig. Fair enough. Jörn -- Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface. -- Doug MacIlroy From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?B?SsO2cm4=?= Engel Subject: Re: [patch 1/15] Makefiles and Kconfig Date: Tue, 8 Apr 2008 15:52:04 +0200 Message-ID: <20080408135203.GB670@logfs.org> References: <20080401181308.512473173@logfs.org> <200804080230.17426.arnd@arndb.de> <20080408083316.GA31262@logfs.org> <200804081542.00333.arnd@arndb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org To: Arnd Bergmann Return-path: Received: from lazybastard.de ([212.112.238.170]:52184 "EHLO longford.logfs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751736AbYDHNwN (ORCPT ); Tue, 8 Apr 2008 09:52:13 -0400 Content-Disposition: inline In-Reply-To: <200804081542.00333.arnd@arndb.de> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tue, 8 April 2008 15:41:59 +0200, Arnd Bergmann wrote: > On Tuesday 08 April 2008, J=C3=B6rn Engel wrote: > > "Logfs file system" might make sense. =C2=A0LOGFS_FS is something I= would > > rather avoid. =C2=A0For some reason my brain reacts strongly to rep= etition, > > redundancy and superfluous information. > >=20 >=20 > How about LOG_FS then? I don't think there is a really good argument > either way, but a large majority uses the *_FS notation in Kconfig. =46air enough. J=C3=B6rn --=20 Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface. -- Doug MacIlroy -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html