linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Oleg Verych <olecom@flower.upol.cz>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	kbuild-devel@lists.sourceforge.net,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-devel] [patch] kbuild: remember ARCH in the object	directory
Date: Tue, 12 Jun 2007 19:12:14 -0700	[thread overview]
Message-ID: <466F527E.1010106@zytor.com> (raw)
In-Reply-To: <20070612180957.GD15329@uranus.ravnborg.org>

Sam Ravnborg wrote:
> 
> If we go the "save important parts of the config" I prefer
> something along the suggestion by hpa with a config file.
> The config file should though be named along the lines
> of Kbuild.config and the syntax should be future proof.
> I like the syntax of the .git/config file and
> it should be along these lines.
> 

It's actually derived from the Windows 3.x config file.  I think it's
massive overkill for this purpose; since the variables can be set on the
command line we're not dealing with multiple namespaces, and it would be
better to have a make-like syntax.

	-hpa

      reply	other threads:[~2007-06-13  2:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09  9:51 [patch 4/9] lguest: the asm offsets akpm
2007-05-09 20:46 ` Sam Ravnborg
2007-05-10  0:09   ` Rusty Russell
2007-06-11 12:49     ` Oleg Verych
2007-06-11 12:59       ` Sam Ravnborg
2007-06-12 10:31         ` [patch] kbuild: remember ARCH in the object directory Oleg Verych
2007-06-12 15:04           ` Randy Dunlap
2007-06-12 16:12           ` Randy Dunlap
2007-06-12 17:19             ` Oleg Verych
2007-06-12 18:09               ` Sam Ravnborg
2007-06-13  2:12                 ` H. Peter Anvin [this message]

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=466F527E.1010106@zytor.com \
    --to=hpa@zytor.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olecom@flower.upol.cz \
    --cc=randy.dunlap@oracle.com \
    --cc=rusty@rustcorp.com.au \
    --cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).