From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>, rmoser <mlmoser@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel source tree splitting
Date: Wed, 30 Apr 2003 21:10:05 -0700 [thread overview]
Message-ID: <9930000.1051762204@[10.10.2.4]> (raw)
In-Reply-To: <20030430172102.69e13ce9.rddunlap@osdl.org>
> I'm probably misreading this...but,
>
> Have you tried this yet? Does it modify/customize all Kconfig
> and Makefiles for the selected tree splits?
>
> A few days ago, in one tree, I rm-ed arch/{all that I don't need}
> and drivers/{all that I don't need}.
> After that I couldn't run "make *config" because it wants all of
> those files, even if I don't want them.
>
> So there are many edits that needed to be done in lots of
> Kconfig and Makefiles if one selectively pulls or omits certain
> sub-directories.
Indeed, I ran across the same thing a while back. Would be *really* nice to
fix, if only so some poor sod over a modem can download a smaller tarball,
or save some diskspace.
M.
next prev parent reply other threads:[~2003-05-01 3:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 23:46 rmoser
2003-05-01 0:21 ` Randy.Dunlap
2003-05-01 0:44 ` rmoser
2003-05-01 2:51 ` Randy.Dunlap
2003-05-01 10:13 ` rmoser
2003-05-01 0:52 ` Larry McVoy
2003-05-01 1:00 ` rmoser
2003-05-01 17:28 ` James H. Cloos Jr.
2003-05-01 4:10 ` Martin J. Bligh [this message]
2003-05-01 6:14 ` Ed Sweetman
2003-05-01 6:14 ` Peter Riocreux
2003-05-02 0:09 ` Randy.Dunlap
2003-05-02 0:41 ` rmoser
2003-05-01 11:54 Chuck Ebbert
2003-05-01 14:06 ` Martin J. Bligh
2003-05-01 14:20 ` Willy TARREAU
2003-05-01 14:35 ` Martin J. Bligh
2003-05-01 14:43 ` Willy TARREAU
2003-05-01 15:01 ` Larry McVoy
2003-05-01 15:11 ` Martin J. Bligh
2003-05-01 17:22 ` Balram Adlakha
2003-05-01 17:28 ` Ben Greear
2003-05-01 20:03 ` John Bradford
2003-05-01 16:00 Chuck Ebbert
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='9930000.1051762204@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mlmoser@comcast.net \
--cc=rddunlap@osdl.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
all inboxes | Powered by JetHome®