All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Watson <tsw@johana.com>
To: linux-kernel@vger.kernel.org
Subject: Pruning the source tree (idea)
Date: Sun, 11 Sep 2005 14:56:39 -0700	[thread overview]
Message-ID: <4324A817.8050004@johana.com> (raw)

In downloading the whole source tree for the 2.6 kernel, I note that 
there is quite a bit of code relating to architectures other than the 
one I'm using.  While this is a "good thing", it does take up space and if
I search for something in the kernel (grep, or some such), the non-used
architectures can take up additional time.

A proposal:
Have a top level make target that prunes (deletes summarily) the 
unwanted architectures from the source tree.  This should be able to be 
done before, or after a config step, but might not be allowed after the 
first make.  Of course, this step is optional, but for those of us who 
only have a single machine type, it would save a bunch of time.

Thanks

(non subscriber)
-- 
Tom Watson		Generic short signature
tsw@johana.com		I'm at home now.


             reply	other threads:[~2005-09-11 21:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-11 21:56 Tom Watson [this message]
2005-09-11 22:20 ` Pruning the source tree (idea) Jesper Juhl
2005-09-12 23:24   ` Rik van Riel
2005-09-13  9:30 ` David Vrabel

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=4324A817.8050004@johana.com \
    --to=tsw@johana.com \
    --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 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.