All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Cc: Taylor Blau <me@ttaylorr.com>, git@vger.kernel.org
Subject: Re: There should have be git gc --repack-arguments
Date: Fri, 9 Apr 2021 16:58:32 +0700	[thread overview]
Message-ID: <1edb799b-5e17-264d-e525-5355c52af36a@gmail.com> (raw)
In-Reply-To: <YG4ws7PiKKKjPUff@coredump.intra.peff.net>

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?

-- 
An old man doll... just what I always wanted! - Clara

  reply	other threads:[~2021-04-09 10:00 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 [this message]
2021-04-09 15:49             ` Jeff King
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=1edb799b-5e17-264d-e525-5355c52af36a@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@ttaylorr.com \
    --cc=peff@peff.net \
    /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.