All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
	akpm@ravnborg.org, Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
	linux-kernel@vger.kernel.org
Subject: Re: kbuild: Separate ouput directory support
Date: Tue, 19 Aug 2003 17:53:33 -0400	[thread overview]
Message-ID: <3F429C5D.4010201@pobox.com> (raw)
In-Reply-To: <20030819214144.GA30978@mars.ravnborg.org>

Sam Ravnborg wrote:
> The following set of patches introduce support for
> separate output directory when building a kernel.
> Typical usage is building several kernels with different configurations -
> but based on the same kernel src.

Thanks, this is some pretty neat stuff.

Is it possible, with your patches, to build from a kernel tree on a 
read-only medium?

	Jeff




  reply	other threads:[~2003-08-19 21:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19 21:41 kbuild: Separate ouput directory support Sam Ravnborg
2003-08-19 21:53 ` Jeff Garzik [this message]
2003-08-19 21:56   ` Sam Ravnborg
2003-08-19 22:13     ` Mike Fedyk
2003-08-21  3:09     ` Chris Friesen
2003-08-21  9:42     ` Geert Uytterhoeven

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=3F429C5D.4010201@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@ravnborg.org \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.