From: Junio C Hamano <gitster@pobox•com>
To: Duy Nguyen <pclouds@gmail•com>
Cc: Martin Fick <mfick@codeaurora•org>,
Git Mailing List <git@vger•kernel.org>
Subject: Re: Ideas to speed up repacking
Date: Tue, 03 Dec 2013 09:50:07 -0800 [thread overview]
Message-ID: <xmqqhaapq0xc.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CACsJy8CBOp_5nwm=WWBG_AZ+h6M7L6WpdX4ACeJxwuJ0kqu0Gw@mail.gmail.com> (Duy Nguyen's message of "Tue, 3 Dec 2013 17:17:57 +0700")
Duy Nguyen <pclouds@gmail•com> writes:
> Reading Martin's mail again I wonder how we just
> "grab all objects and skip history traversal". Who will decide object
> order in the new pack if we don't traverse history and collect path
> information.
I vaguely recall raising a related topic for "quick repack, assuming
everything in existing packfiles are reachable, that only removes
loose cruft" several weeks ago. Once you decide that your quick
repack do not care about ejecting objects from existing packs, like
how I suspect Martin's outline will lead us to, we can repack the
reachable loose ones on the recent surface of the history and then
concatenate the contents of existing packs, excluding duplicates and
possibly adjusting the delta base offsets for some entries, without
traversing the bulk of the history.
next prev parent reply other threads:[~2013-12-03 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 23:30 Ideas to speed up repacking Martin Fick
2013-12-03 0:44 ` Junio C Hamano
2013-12-03 3:27 ` Duy Nguyen
2013-12-03 7:17 ` Junio C Hamano
2013-12-03 10:17 ` Duy Nguyen
2013-12-03 17:50 ` Junio C Hamano [this message]
2013-12-03 19:26 ` Martin Fick
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=xmqqhaapq0xc.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mfick@codeaurora$(echo .)org \
--cc=pclouds@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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