From: Jonathan Tan <jonathantanmy@google.com>
To: git@vger.kernel.org
Cc: Jonathan Tan <jonathantanmy@google.com>
Subject: [PATCH 0/2] Repacking of promisor packfiles
Date: Tue, 7 Aug 2018 13:12:30 -0700 [thread overview]
Message-ID: <cover.1533672584.git.jonathantanmy@google.com> (raw)
These patches teach Git to also repack promisor packfiles upon GC, which
reduces one of the pain points of current partial clone usage (many
promisor packfiles in the objects/pack/ directory, generated upon each
fetch).
In the t/ tests, I strived to verify that repack doesn't accidentally
delete any objects. Let me know if you can think of better ways to do
that.
Jonathan Tan (2):
repack: refactor setup of pack-objects cmd
repack: repack promisor objects if -a or -A is set
Documentation/git-repack.txt | 5 ++
builtin/repack.c | 163 ++++++++++++++++++++++++-----------
t/t0410-partial-clone.sh | 71 ++++++++++++---
3 files changed, 180 insertions(+), 59 deletions(-)
--
2.18.0.597.ga71716f1ad-goog
next reply other threads:[~2018-08-07 20:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 20:12 Jonathan Tan [this message]
2018-08-07 20:12 ` [PATCH 1/2] repack: refactor setup of pack-objects cmd Jonathan Tan
2018-08-07 20:12 ` [PATCH 2/2] repack: repack promisor objects if -a or -A is set Jonathan Tan
2018-08-07 20:57 ` Junio C Hamano
2018-08-07 23:23 ` Jonathan Tan
2018-08-08 0:25 ` Junio C Hamano
2018-08-08 18:45 ` Jonathan Tan
2018-08-08 15:50 ` Jeff King
2018-08-08 16:17 ` Junio C Hamano
2018-08-07 22:37 ` Junio C Hamano
2018-08-07 23:25 ` Jonathan Tan
2018-08-08 16:34 ` Junio C Hamano
2018-08-08 22:34 ` [PATCH v2 0/2] Repacking of promisor packfiles Jonathan Tan
2018-08-08 22:34 ` [PATCH v2 1/2] repack: refactor setup of pack-objects cmd Jonathan Tan
2018-08-08 22:34 ` [PATCH v2 2/2] repack: repack promisor objects if -a or -A is set Jonathan Tan
2018-08-09 17:05 ` Junio C Hamano
2018-08-09 18:12 ` Jonathan Tan
2018-08-18 16:05 ` Duy Nguyen
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=cover.1533672584.git.jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--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 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).