From: David Woodhouse <dwmw2@infradead.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Announce: Kernel Build for 2.5, Release 1.1 is available.
Date: Sun, 12 Aug 2001 15:56:07 +0100 [thread overview]
Message-ID: <21969.997628167@redhat.com> (raw)
In-Reply-To: <3742.997627694@ocs3.ocs-net>
In-Reply-To: <3742.997627694@ocs3.ocs-net>
kaos@ocs.com.au said:
> If you allow creation of a file in one directory but storing it in
> another then you have to search all makefiles to find out what is
> created in any directory. Horrible!
Fine. But what's stopping us from putting a makefile in the
asm-$(ARCH)/include directory? There are already automatically generated
files in there. What have you already done for stuff like
asm-arm/mach-types.h?
--
dwmw2
next prev parent reply other threads:[~2001-08-12 14:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-11 15:03 Announce: Kernel Build for 2.5, Release 1.1 is available Keith Owens
2001-08-11 15:20 ` Russell King
2001-08-11 16:03 ` Keith Owens
2001-08-11 16:08 ` Philip Blundell
2001-08-11 16:14 ` Russell King
2001-08-11 21:35 ` [kbuild-devel] " Tom Rini
2001-08-11 21:55 ` Roman Zippel
2001-08-12 1:17 ` Keith Owens
2001-08-11 22:02 ` [kbuild-devel] " Tom Rini
2001-08-12 1:21 ` Keith Owens
2001-08-12 1:44 ` Tom Rini
2001-08-12 14:36 ` David Woodhouse
2001-08-12 14:48 ` Keith Owens
2001-08-12 14:56 ` David Woodhouse [this message]
2001-08-12 14:56 ` Russell King
2001-08-13 2:23 ` Keith Owens
2001-08-12 2:24 ` Keith Owens
2001-08-12 4:30 ` Keith Owens
2001-08-19 7:13 ` Richard Henderson
[not found] <20010811212051.A819@jaquet.dk>
2001-08-12 2:11 ` Keith Owens
2001-08-12 2:27 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2001-08-12 7:31 [kbuild-devel] " Rasmus Andersen
2001-08-12 7:44 ` Keith Owens
2001-08-12 7:57 ` Daniel T. Chen
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=21969.997628167@redhat.com \
--to=dwmw2@infradead.org \
--cc=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.net \
--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