From: Jeff King <peff@peff.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Taylor Blau <me@ttaylorr.com>,
git@vger.kernel.org
Subject: Re: There should have be git gc --repack-arguments
Date: Fri, 9 Apr 2021 11:49:11 -0400 [thread overview]
Message-ID: <YHB3d31eTACBd6pY@coredump.intra.peff.net> (raw)
In-Reply-To: <1edb799b-5e17-264d-e525-5355c52af36a@gmail.com>
On Fri, Apr 09, 2021 at 04:58:32PM +0700, Bagas Sanjaya wrote:
> On 08/04/21 05.22, Jeff King wrote:
> > If you are sneaker-netting, you are probably better off to just split
> > the pack at byte boundaries with an external tool anyway, for two
> > reasons:
> >
> > - our max-pack-size is just a guideline. It only splits at object
> > boundaries so if you have an object bigger than the max, we'll
> > exceed it.
> >
> > - dedicated splitting tools often have useful extra features, like
> > k-of-n error correction.
> >
> What external tools are for splitting packs? Can splitted packs
> by such tools still be usable by Git?
No, but you can reassemble the parts at the destination before feeding
them to Git. On a system with normal posix tools, you can split like:
git pack-objects --stdout --all </dev/null |
split -b 1m - split-pack-
and then after transferring split-pack-* (which are individual 1
megabyte files) to the destination, you can do:
cat split-pack-* |
git index-pack -v --stdin
(There's no error correction in split; tools like rar will do that, and
probably others, but it has been ages since I've had to split a file to
meet transfer requirements).
-Peff
next prev parent reply other threads:[~2021-04-09 15:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 12:10 There should have be git gc --repack-arguments Bagas Sanjaya
2021-04-07 19:37 ` Jeff King
2021-04-07 20:40 ` Junio C Hamano
2021-04-07 21:37 ` Jeff King
2021-04-07 22:13 ` Junio C Hamano
2021-04-07 22:22 ` Jeff King
2021-04-09 9:58 ` Bagas Sanjaya
2021-04-09 15:49 ` Jeff King [this message]
2021-04-07 19:38 ` Bryan Turner
2021-04-08 13:31 ` Bagas Sanjaya
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=YHB3d31eTACBd6pY@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.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).