mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: linux kernel conf 0.8
Date: Wed, 9 Oct 2002 19:16:00 +0200	[thread overview]
Message-ID: <20021009191600.A1708@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0210091243240.338-100000@serv>; from zippel@linux-m68k.org on Wed, Oct 09, 2002 at 02:01:50PM +0200

On Wed, Oct 09, 2002 at 02:01:50PM +0200, Roman Zippel wrote:

> On Tue, 8 Oct 2002, Linus Torvalds wrote:
> > Some things made me go eww (but on the whole details):
> >
> >  - I'd prefer the Config.in name, since this has nothing to do with
> >    building, and everything to do with configuration.

Another suggestion about naming:
Take for example drivers/net:
cat Config.* | wc => 2149 lines

A bit a structure could be needed here.
Net.conf  <= Name equals directory with upper-case first letter
	- Cover the whole directory, and either implicit
	  or explicit include other .conf files in that directory
3c5xx.conf <= All the configuration for the 3c5xxx chipset drivers
rrunner.conf <= All configuration for rrunner driver

So letting the naming convention be directory name with upper-case start
letter - as the entry to a directory.
Additional configuration in sensibly named configuration files.
I do not see the split of configuration happen before 2.6, except in 
some special cases though. But I wanted to let the naming convention
support that.

source statements could look like:
source driver/net  <= since Net.conf is implicit
But I would prefer the files spelled out. 

> On Tue, 8 Oct 2002, Linus Torvalds wrote:
> >  - I assume that the scripts are generated from the current Config.in
> >    and Config.help files, and it would make me slightly happier to see the
> >    diff as a "automatic script" + "diff to fix it up", just for doc
> >    purposes.
> 
> All this is in the archive.

Keep both versions please. It's much easier just to apply a patch,
but I see why Linus ask for the other solution.
I know what version has preference ;-)

	Sam

  parent reply	other threads:[~2002-10-09 17:11 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0210081830350.4396-100000@home.transmeta.com>
2002-10-09 12:01 ` Roman Zippel
2002-10-09 13:35   ` Jeff Garzik
2002-10-09 13:55     ` Roman Zippel
2002-10-09 14:07       ` Jeff Garzik
2002-10-09 14:14       ` [kbuild-devel] " Brendan J Simon
2002-10-09 14:28         ` Jeff Garzik
2002-10-09 14:24   ` Brendan J Simon
2002-10-09 14:34     ` Randy.Dunlap
2002-10-09 14:45       ` J.A. Magallon
2002-10-09 15:14         ` Roman Zippel
2002-10-09 15:16       ` Linus Torvalds
2002-10-09 15:19         ` Randy.Dunlap
2002-10-09 16:29           ` Roman Zippel
2002-10-09 16:40             ` Christoph Hellwig
2002-10-09 18:39               ` Roman Zippel
2002-10-09 18:52                 ` Peter Samuelson
2002-10-09 19:28                   ` Randy.Dunlap
2002-10-09 19:39                     ` Sam Ravnborg
2002-10-09 19:47                       ` Randy.Dunlap
2002-10-09 14:55     ` [kbuild-devel] " Roman Zippel
2002-10-09 17:16   ` Sam Ravnborg [this message]
2002-10-09 17:37     ` Linus Torvalds
2002-10-09 17:55       ` Sam Ravnborg
2002-10-09 18:47         ` Linus Torvalds
2002-10-09 19:26           ` Sam Ravnborg
2002-10-09 20:41             ` Jeff Garzik
2002-10-09 22:49               ` Roman Zippel
2002-10-10 14:18                 ` Jeff Garzik
2002-10-10 17:29                   ` Sam Ravnborg
2002-10-10 17:32                     ` Jeff Garzik
2002-10-10 17:51                       ` Sam Ravnborg
2002-10-09 23:49         ` [kbuild-devel] " Brendan J Simon
2002-10-09 18:35       ` Jeff Garzik
2002-10-09  0:40 Roman Zippel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021009191600.A1708@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=zippel@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®