From: Christoph Hellwig <hch@infradead.org>
To: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
linux-arch@vger.kernel.org
Subject: Re: New kbuild filename: Kbuild
Date: Fri, 29 Oct 2004 12:59:03 +0100 [thread overview]
Message-ID: <20041029115903.GC11391@infradead.org> (raw)
In-Reply-To: <20041028190020.GB9004@mars.ravnborg.org>
On Thu, Oct 28, 2004 at 09:00:20PM +0200, Sam Ravnborg wrote:
> kbuild: Prefer Kbuild as name of the kbuild files
>
> The kbuild syntax is unique and does only have very few things in common with
> usual Makefile syntax. So to avoid confusion make the filename 'Kbuild' be
> the preferred name as replacement for 'Makefile'.
> No global renaming planned to take place for now, but new stuff expected to use
> the new 'Kbuild' filename.
Disagree. These are just makefiles, and renaming for the sake of it
doesn't buy us. If you really want to improve things implement something like
module foo.ko
sources foo.c blah.c
sources foobar.c if FOO_BAR
in Kconfig and get rid of driver makefiles compeltely
next prev parent reply other threads:[~2004-10-29 11:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 18:59 kbuild/all archs: Sanitize creating offsets.h Sam Ravnborg
2004-10-28 19:00 ` New kbuild filename: Kbuild Sam Ravnborg
2004-10-28 17:30 ` Geert Uytterhoeven
2004-10-29 11:59 ` Christoph Hellwig [this message]
2004-10-29 19:12 ` Sam Ravnborg
2004-10-29 17:47 ` Roman Zippel
2004-10-29 20:46 ` Sam Ravnborg
2004-10-28 19:01 ` kbuild: generic support for offsets.h Sam Ravnborg
2004-10-28 19:02 ` i386: use " Sam Ravnborg
2004-10-29 9:52 ` Jan-Benedict Glaw
2004-10-29 19:05 ` Sam Ravnborg
2004-10-28 19:03 ` arm: use generic support for constants.h Sam Ravnborg
2004-10-28 19:44 ` kbuild/all archs: Sanitize creating offsets.h Russell King
2004-10-28 21:59 ` Sam Ravnborg
2004-10-28 21:00 ` Russell King
2004-10-28 23:45 ` Sam Ravnborg
2004-10-29 21:28 ` Sam Ravnborg
2004-10-29 19:51 ` Russell King
2004-10-29 22:36 ` Sam Ravnborg
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=20041029115903.GC11391@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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