public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Giacomo Catenazzi <cate@dplanet.ch>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Giacomo Catenazzi <cate@debian.org>,
	andersen@codepoet.org, Roman Zippel <zippel@linux-m68k.org>,
	linux-kernel@vger.kernel.org
Subject: Re: linux kernel config converter
Date: Thu, 21 Feb 2002 15:39:49 +0100	[thread overview]
Message-ID: <3C7506B5.20103@dplanet.ch> (raw)
In-Reply-To: <fa.fsgrt4v.1bngh9t@ifi.uio.no> <fa.hp69onv.i7qtq3@ifi.uio.no> <3C74FF03.8070502@debian.org> <3C7503B1.E7CA83AA@mandrakesoft.com>


Jeff Garzik wrote:

>> 
> For directories like kernel/* and mm/* and arch/*, I imagine that down
> the road we will want kernel.conf and mm.conf too, though right now they
> would probably remain as makefiles...
> 
> If you look closely at the problem, you will see there is no fundamental
> reason why we cannot package makefile rules like we want to package
> config information.


I agree that in most case (drivers) it is the right thing.
But for kernel/, arch/ there are no simple way to tell:
"this makefile rule belong to this configuration".
In such cases we should not split makefiles and configurations
in an artificial way.
We should not generalize and split configuration and makefile
just because in most case it is the right thing.

[ Some Makefile define at the beginning some flags that
   should be used for all driver in such subdir.
   These info should be in a 'main' .conf (main = where normal
   user would check, without grep to all .conf)
  ]

	giacomo


  reply	other threads:[~2002-02-21 14:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.fsgrt4v.1bngh9t@ifi.uio.no>
     [not found] ` <fa.hp69onv.i7qtq3@ifi.uio.no>
2002-02-21 14:06   ` linux kernel config converter Giacomo Catenazzi
2002-02-21 14:26     ` Jeff Garzik
2002-02-21 14:39       ` Giacomo Catenazzi [this message]
2002-02-21 15:11         ` Jeff Garzik
2002-02-21 16:00       ` Randy.Dunlap
     [not found]   ` <fa.lqt3hav.190o1i9@ifi.uio.no>
2002-02-21 14:50     ` Giacomo Catenazzi
2002-02-21 14:56       ` David Lang
2002-02-21 15:05         ` Giacomo Catenazzi
     [not found] <fa.gq2s5iv.1s4in@ifi.uio.no>
2002-02-21 13:28 ` Giacomo Catenazzi
2002-02-21 14:11   ` Roman Zippel
2002-02-21 14:32     ` Giacomo Catenazzi
2002-02-21 15:19       ` Roman Zippel
2002-02-21 10:48 Roman Zippel
2002-02-21 11:40 ` Jeff Garzik
2002-02-21 12:21   ` Roman Zippel
2002-02-21 12:32     ` Jeff Garzik
2002-02-21 12:54 ` Erik Andersen
2002-02-21 13:21   ` Jeff Garzik
2002-02-21 14:28     ` David Lang
2002-02-21 14:36       ` Jeff Garzik
2002-02-21 14:40         ` David Lang
2002-02-21 15:05           ` Jeff Garzik
2002-02-21 15:41             ` Jason Lunz
2002-02-21 15:54               ` Jeff Garzik
2002-02-21 15:18         ` Alan Cox
2002-02-21 15:08           ` Jeff Garzik
2002-02-21 15:22             ` Gerd Knorr
2002-02-21 15:33       ` Roman Zippel
2002-02-21 18:53     ` Andreas Dilger

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=3C7506B5.20103@dplanet.ch \
    --to=cate@dplanet.ch \
    --cc=andersen@codepoet.org \
    --cc=cate@debian.org \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --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