git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Mark Levedahl <mlevedahl@gmail.com>,
	Junio C Hamano <junkio@cox.net>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-bundle: Make thin packs
Date: Wed, 7 Mar 2007 16:34:16 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0703071632140.5963@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0703080121210.22628@wbgn013.biozentrum.uni-wuerzburg.de>



On Thu, 8 Mar 2007, Johannes Schindelin wrote:
>
> 	> Since a bundle doesn't make any sense *anyway* unless you have 
> 	> the prerequisites at the other end, I think you might as well do 
> 	> thin packs. That will cut down on the bundle size a *lot* for 
> 	> the common cases.
> 
> 	Well, I disagree on the blanket "*anyway*". Shallow fetches are no 
> 	longer possible from these bundles (at least after this commit 
> 	_and_ ":/git-bundle: avoid packing" which I just sent out).

Does anybody actually use shallow clones in real life?

When I did the numbers a long time ago, the shallow clone didn't actually 
help much, because it meant that there were no deltas. Which meant that 
you got 1% of the history for 60% of the price of all history, and the 
shallow thing didn't really seem to make much sense.

I guess that for something with a really long history, you'd get 0.001% of 
the history for 10% of the price, and maybe it makes sense then.

		Linus

  reply	other threads:[~2007-03-08  0:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06  4:17 builtin git-bundle - pack contains many more objects than required Mark Levedahl
2007-03-06  6:18 ` Junio C Hamano
2007-03-06  7:45 ` [PATCH] git-bundle: fix pack generation Junio C Hamano
2007-03-07  1:15   ` Mark Levedahl
2007-03-07  3:01     ` Junio C Hamano
2007-03-07  3:17       ` Mark Levedahl
2007-03-07  3:22         ` Johannes Schindelin
2007-03-07  3:50           ` Mark Levedahl
2007-03-07  4:05             ` Johannes Schindelin
2007-03-07  5:57               ` Junio C Hamano
2007-03-07 16:34               ` Mark Levedahl
2007-03-07 22:35                 ` Johannes Schindelin
2007-03-07 23:17                   ` Linus Torvalds
2007-03-08  0:27                     ` [PATCH] git-bundle: Make thin packs Johannes Schindelin
2007-03-08  0:34                       ` Linus Torvalds [this message]
2007-03-08  0:56                         ` Johannes Schindelin
2007-03-08  2:02                       ` Junio C Hamano
2007-03-08 13:07                         ` Johannes Schindelin
2007-03-07 23:32                   ` [PATCH] git-bundle: fix pack generation Junio C Hamano
2007-03-07 23:43                     ` [PATCH] git-bundle: avoid packing objects which are in the prerequisites Johannes Schindelin
2007-03-08 20:36                       ` Mark Levedahl
2007-03-07  1:16   ` [PATCH] git-bundle: fix pack generation Mark Levedahl

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=Pine.LNX.4.64.0703071632140.5963@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=mlevedahl@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).