From: Dave Jones <davej@suse.de>
To: Josh Fryman <fryman@cc.gatech.edu>
Cc: Christer Weinigel <wingel@acolyte.hack.org>,
gone@us.ibm.com, linux-kernel@vger.kernel.org,
lse-tech@lists.sourceforge.net
Subject: Re: [RFC] modularization of i386 setup_arch and mem_init in 2.4.18
Date: Sat, 9 Mar 2002 02:21:59 +0100 [thread overview]
Message-ID: <20020309022158.E15106@suse.de> (raw)
In-Reply-To: <200203082108.g28L8I504672@w-gaughen.des.beaverton.ibm.com> <20020308223330.A15106@suse.de> <20020308234811.3F003F5B@acolyte.hack.org> <20020308201518.533dc16a.fryman@cc.gatech.edu>
In-Reply-To: <20020308201518.533dc16a.fryman@cc.gatech.edu>; from fryman@cc.gatech.edu on Fri, Mar 08, 2002 at 08:15:18PM -0500
On Fri, Mar 08, 2002 at 08:15:18PM -0500, Josh Fryman wrote:
> excuse me for intruding a bit, but in the restructuring of kernel 2.5.x, is
> there any notion of separating the build directories from the source
> directories? if you're all hacking up the tree org anyway, this would be a
> nice feature... (somewhat like gcc, i guess)
Sounds like you want the shadow tree feature of kbuild-2.5
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-03-09 1:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 21:08 [RFC] modularization of i386 setup_arch and mem_init in 2.4.18 Patricia Gaughen
2002-03-08 21:33 ` Dave Jones
2002-03-08 21:34 ` Greg KH
2002-03-08 21:59 ` [Lse-tech] " Martin J. Bligh
2002-03-08 22:16 ` Dave Jones
2002-03-09 0:00 ` H. Peter Anvin
2002-03-08 23:48 ` Christer Weinigel
2002-03-09 1:15 ` Josh Fryman
2002-03-09 1:21 ` Dave Jones [this message]
2002-03-09 1:22 ` Christer Weinigel
2002-03-10 7:27 ` Eric W. Biederman
2002-03-09 7:22 ` [Lse-tech] " Christoph Hellwig
2002-03-10 7:42 ` Eric W. Biederman
2002-03-10 13:08 ` Alan Cox
2002-03-11 3:17 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2002-03-08 22:54 James Bottomley
2002-03-11 16:51 James Bottomley
2002-03-12 3:43 ` James Bottomley
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=20020309022158.E15106@suse.de \
--to=davej@suse.de \
--cc=fryman@cc.gatech.edu \
--cc=gone@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=wingel@acolyte.hack.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