From: Shawn Pearce <spearce@spearce.org>
To: Timur Tabi <timur@freescale.com>
Cc: git@vger.kernel.org
Subject: Re: Is there a way to trim old SHAs from a git tree (so it's not so large)?
Date: Wed, 15 Nov 2006 17:33:00 -0500 [thread overview]
Message-ID: <20061115223300.GF24861@spearce.org> (raw)
In-Reply-To: <455B9411.4090708@freescale.com>
Timur Tabi <timur@freescale.com> wrote:
> Shawn Pearce wrote:
>
> >Have you tried "git repack -a -d" to repack the loose objects into
> >a pack file? Doing this every so often should reduce your disk
> >space consumed by a HUGE amount.
>
> Woah! It shrunk that bad boy down to 420M! That should do it, thanks!
>
> I wonder why the powerpc tree shrank so much. Do you think the maintainer
> just needs to run git-repack on his tree?
Possible, yes.
However published repositories don't tend to repack as often as
it makes things harder for people who clone/fetch over HTTP rather
than the native git protocol.
The reason is that HTTP can fetch individual loose objects that
you don't have yet, but if the object is only available in a pack
file then you need to fetch the entire pack file. But you might
already have most of that pack file, so now you are downloading
lots of data you already have. :-(
--
next prev parent reply other threads:[~2006-11-15 22:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 22:11 Is there a way to trim old SHAs from a git tree (so it's not so large)? Timur Tabi
2006-11-15 22:16 ` Shawn Pearce
2006-11-15 22:26 ` Timur Tabi
2006-11-15 22:33 ` Shawn Pearce [this message]
2006-11-17 10:36 ` Thomas Kolejka
2006-11-21 16:29 ` Timur Tabi
2006-11-21 16:32 ` Shawn Pearce
2006-11-21 16:52 ` Timur Tabi
2006-11-21 16:56 ` Shawn Pearce
2006-11-21 17:01 ` Timur Tabi
2006-11-21 18:39 ` Shawn Pearce
2006-11-21 21:49 ` Timur Tabi
2006-11-21 22:06 ` Johannes Schindelin
2006-11-21 22:47 ` Timur Tabi
2006-11-21 22:53 ` Jakub Narebski
2006-11-21 22:53 ` Johannes Schindelin
2006-11-21 23:12 ` Timur Tabi
2006-11-21 23:22 ` Jakub Narebski
2006-11-21 16:57 ` Johannes Schindelin
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=20061115223300.GF24861@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=timur@freescale.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).