From: Eric Wong <e@80x24.org>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jeff King <peff@peff.net>
Subject: Re: Git packs friendly to block-level deduplication
Date: Wed, 24 Jan 2018 22:25:18 +0000 [thread overview]
Message-ID: <20180124222518.GA24157@whir> (raw)
In-Reply-To: <87bmhiykvw.fsf@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
> If you have a bunch of git repositories cloned of the same project on
> the same filesystem, it would be nice of the packs that are produced
> would be friendly to block-level deduplication.
Fwiw, I currently get around this when mirroring by having all
the remotes I care about mirrored to a "hidden" root repo, and
having other repos point to the hidden root objects via
object/info/alternates. Not that great for usability and
probably potentially racy...
> Has anyone here barked up this tree before? Suggestions? Tips on where
> to start hacking the repack code to accomplish this would be most
> welcome.
The Debian version of gzip(1) has an --rsyncable patch which
might be of help.
next prev parent reply other threads:[~2018-01-24 22:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 22:03 Git packs friendly to block-level deduplication Ævar Arnfjörð Bjarmason
2018-01-24 22:19 ` Mike Hommey
2018-01-24 22:23 ` Junio C Hamano
2018-01-24 22:30 ` Mike Hommey
2018-01-24 22:47 ` Ævar Arnfjörð Bjarmason
2018-01-24 22:25 ` Eric Wong [this message]
2018-01-24 22:37 ` Elijah Newren
2018-01-24 23:06 ` Ævar Arnfjörð Bjarmason
2018-01-24 23:32 ` Jeff King
2018-01-24 23:22 ` Jeff King
2018-01-25 0:03 ` Ævar Arnfjörð Bjarmason
2018-01-25 0:10 ` Jeff King
2018-01-25 0:29 ` Jeff King
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=20180124222518.GA24157@whir \
--to=e@80x24.org \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).