All of lore.kernel.org
 help / color / mirror / Atom feed
From: Balram Adlakha <b_adlakha@softhome.net>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel source tree splitting
Date: Thu, 1 May 2003 22:52:38 +0530	[thread overview]
Message-ID: <20030501172238.GA13756@localhost.localdomain> (raw)
In-Reply-To: <200305010756_MC3-1-36E1-623@compuserve.com>

[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]

On Thu, May 01, 2003 at 07:54:03AM -0400, Chuck Ebbert wrote:
> Martin J. Bligh wrote:
> 
> >> 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.
> 
>  I have seven source trees on disk right now.  Getting rid off all
> the archs but i386 would not only save tons of space, it would also
> make 'grep -r' go faster and stop spewing irrelevant hits for archs
> that I couldn't care less about.
> 
> 
> ------
>  Chuck
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

I agree with you. Making different trees for different archs will make the tarball much smaller. Usually people only use one architecture and the other code lies waste. I think this has been discussed many times but It really is worth doing.
-- 

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-05-01 17:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01 11:54 Kernel source tree splitting 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 [this message]
2003-05-01 17:28   ` Ben Greear
2003-05-01 20:03     ` John Bradford
  -- strict thread matches above, loose matches on Subject: below --
2003-05-01 16:00 Chuck Ebbert
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
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

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=20030501172238.GA13756@localhost.localdomain \
    --to=b_adlakha@softhome.net \
    --cc=76306.1226@compuserve.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.