From: Thomas <th.acker66@arcor.de>
To: git@vger.kernel.org
Subject: Re: Large repo and pack.packsizelimit
Date: Thu, 10 May 2012 11:42:09 +0000 (UTC) [thread overview]
Message-ID: <loom.20120510T133639-197@post.gmane.org> (raw)
In-Reply-To: 7vlil1tg7w.fsf@alter.siamese.dyndns.org
Junio C Hamano <gitster <at> pobox.com> writes:
>
> Thomas <th.acker66 <at> arcor.de> writes:
>
> > (1) all objects to be transferred to another repo
> > (2) all loose objects when starting a local repack
> > Case (1) can be fixed by transfer.unpacklimit but there is no fix for (2).
>
> Technically (1) is putting everything in a single pack to transfer, and it
> is only the receiving end that does the chopping.
>
> For (2), you could do something like
>
> keep=$( git rev-list --objects $some_rev |
> git pack-objects --delta-base-offset pack ) &&
> mv pack-$keep.pack pack-$keep.idx .git/objects/pack/ &&
> echo "keep $some_rev" >.git/objects/pack/pack-$keep.keep
>
> after finding a suitable $some_rev that is old enough so that it will be
> an ancestor of anything that matters in the future and gives small enough
> packfiles. You may want to try doing the above multiple times, by picking
> a few strategic ranges, e.g.
>
> for some_rev in v1.0 v1.0..v2.0 v2.0..v2.4 v2.4..v3.0
> do
> ... the above four lines come here ...
> done
>
Not really a porcelain-level solution ;-) but I will try it.
Thanks!
Is there any chance that (1) and (2) will be solved by using packsizelimit
in the future?
Will there be any porcelain/plumbing commands for creating/deleting
.keep files for packs?
---
Thomas
prev parent reply other threads:[~2012-05-10 11:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 11:57 Large repo and pack.packsizelimit th.acker66
2012-05-08 20:31 ` Jeff King
2012-05-08 21:13 ` Nicolas Pitre
2012-05-08 21:20 ` Jeff King
2012-05-08 21:52 ` Nicolas Pitre
2012-05-09 9:36 ` Thomas
2012-05-09 10:50 ` Nguyen Thai Ngoc Duy
2012-05-09 11:46 ` Thomas
2012-05-09 17:30 ` Junio C Hamano
2012-05-10 11:42 ` Thomas [this message]
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=loom.20120510T133639-197@post.gmane.org \
--to=th.acker66@arcor.de \
--cc=git@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.