From: Keith Owens <kaos@ocs.com.au>
To: "M. R. Brown" <mrbrown@0xd6.org>
Cc: linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: Any arch specific changes to scripts directory?
Date: Thu, 13 Dec 2001 17:05:25 +1100 [thread overview]
Message-ID: <24711.1008223525@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 12 Dec 2001 23:59:43 MDT." <20011213055943.GB7669@0xd6.org>
On Wed, 12 Dec 2001 23:59:43 -0600,
"M. R. Brown" <mrbrown@0xd6.org> wrote:
>On an somewhat-related subject, here are a couple of utility scripts that
>make it easier to use drop-in trees with various stock kernels. These are
>used by linux-mips, linuxconsole (Ruby), and linuxsh developers, so it's
>assumed they'd be useful to anyone else who needs to build those kernels.
This facility and more is built into kbuild 2.5, which is going into
2.5 soon. I don't see the point in adding this to 2.4 now, especially
since kbuild 2.5 can also run on 2.4 kernels.
http://sourceforge.net/projects/kbuild
next prev parent reply other threads:[~2001-12-13 6:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 23:09 Any arch specific changes to scripts directory? Keith Owens
2001-12-13 5:59 ` M. R. Brown
2001-12-13 6:05 ` Keith Owens [this message]
2001-12-13 17:18 ` M. R. Brown
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=24711.1008223525@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mrbrown@0xd6.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