From: Sean <seanlkml@sympatico.ca>
To: David Lang <dlang@digitalinsight.com>
Cc: Dave Jones <davej@redhat.com>, Dax Kelson <dax@gurulabs.com>,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Linux kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: Smaller compressed kernel source tarballs?
Date: Thu, 21 Sep 2006 19:38:23 -0400 [thread overview]
Message-ID: <BAYC1-PASMTP07CBA42AB1F6D00285C35CAE200@CEZ.ICE> (raw)
Message-ID: <20060921193823.ec49d446.seanlkml@sympatico.ca> (raw)
In-Reply-To: <Pine.LNX.4.63.0609211530180.17238@qynat.qvtvafvgr.pbz>
On Thu, 21 Sep 2006 15:34:53 -0700 (PDT)
David Lang <dlang@digitalinsight.com> wrote:
> I was responding to the (apparent) argument that with git and ketchup people
> should not ever be downloading tarballs, so something that cuts the size of a
> tarball in half doesn't make any difference.
Sure there are some cases where tarballs are more appropriate, but with git
and maybe some of the other tools it should really be the minority situation.
I wonder how many people just use tarballs out of inertia. All said though
saving a few bytes of bandwidth by making the tarballs smaller can't hurt.
Sean
next prev parent reply other threads:[~2006-09-21 23:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 20:32 Dax Kelson
[not found] ` <20060921204250 .GN13641@csclub.uwaterloo.ca>
2006-09-21 20:42 ` Lennart Sorensen
[not found] ` <20060921171747.9ae2b42e.seanlkml@sympatico.ca>
2006-09-21 21:17 ` Sean
2006-09-21 21:41 ` Dax Kelson
2006-09-21 21:50 ` Bob Copeland
[not found] ` <20060921175717.272c58ee.seanlkml@sympatico.ca>
2006-09-21 21:57 ` Sean
2006-09-21 22:00 ` David Lang
2006-09-21 22:24 ` Dave Jones
2006-09-21 22:16 ` David Lang
2006-09-21 22:40 ` Dave Jones
2006-09-21 22:34 ` David Lang
[not found] ` <20060921193823.ec49d446.seanlkml@sympatico.ca>
2006-09-21 23:38 ` Sean [this message]
[not found] ` <Pin e.LNX.4.63.0609211455570.17238@qynat.qvtvafvgr.pbz>
2006-09-21 22:25 ` Sean
[not found] ` <20060921182554.23044ca3.seanlkml@sympatico.ca>
2006-09-21 22:20 ` David Lang
2006-09-21 21:40 ` Dax Kelson
2006-09-22 14:00 ` Lennart Sorensen
2006-09-21 21:43 ` H. Peter Anvin
2006-09-22 14:00 ` Lennart Sorensen
2006-09-22 16:13 ` H. Peter Anvin
2006-09-22 16:13 ` Jan Engelhardt
2006-09-22 16:33 ` H. Peter Anvin
2006-09-22 17:41 ` Johannes Stezenbach
2006-09-22 18:09 ` H. Peter Anvin
2006-09-22 18:19 ` Michael Tokarev
2006-09-22 18:26 ` H. Peter Anvin
2006-09-25 11:51 ` Paulo Marques
2006-09-25 15:47 ` H. Peter Anvin
2006-10-02 3:35 Drew Scott Daniels
2006-10-02 3:32 ` Bernd Eckenfels
2006-10-02 3:35 ` Willy Tarreau
[not found] ` <Pi ne.LNX.4.63.0610012205280.28534@qynat.qvtvafvgr.pbz>
2006-10-02 5:11 ` David Lang
2006-10-02 5:49 ` Willy Tarreau
2006-10-02 15:16 ` Phillip Susi
2006-10-02 15:48 ` David Lang
2006-10-02 20:20 ` Phillip Susi
2006-10-02 20:12 ` David Lang
2006-10-02 20:35 ` Willy Tarreau
[not found] ` <2006 1002203527.GA585@1wt.eu>
2006-10-02 21:49 ` Sean
[not found] ` <20061002174938.bb82027d.seanlkml@sympatico.ca>
2006-10-02 21:42 ` David Lang
2006-10-03 2:48 ` Willy Tarreau
2006-10-03 10:28 ` Jan Engelhardt
2006-10-03 18:24 ` Phillip Susi
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=BAYC1-PASMTP07CBA42AB1F6D00285C35CAE200@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=davej@redhat.com \
--cc=dax@gurulabs.com \
--cc=dlang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--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 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®