From: David Turner <dturner@twosigma.com>
To: git@vger.kernel.org, peff@peff.net, j6t@kgdb.org
Cc: David Turner <dturner@twosigma.com>
Subject: [PATCH v5 0/2] repack (oops)
Date: Wed, 28 Dec 2016 17:45:40 -0500 [thread overview]
Message-ID: <1482965142-6778-1-git-send-email-dturner@twosigma.com> (raw)
This version addresses Johannes Sixt's comments on v4. Also, I
messed up the rebase on v4.
David Turner (2):
auto gc: don't write bitmaps for incremental repacks
repack: die on incremental + write-bitmap-index
builtin/gc.c | 9 ++++++++-
builtin/repack.c | 9 +++++++++
t/t5310-pack-bitmaps.sh | 8 +++-----
t/t6500-gc.sh | 25 +++++++++++++++++++++++++
4 files changed, 45 insertions(+), 6 deletions(-)
--
2.8.0.rc4.22.g8ae061a
next reply other threads:[~2016-12-28 22:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 22:45 David Turner [this message]
2016-12-28 22:45 ` [PATCH v5 1/2] auto gc: don't write bitmaps for incremental repacks David Turner
2016-12-28 22:45 ` [PATCH v5 2/2] repack: die on incremental + write-bitmap-index David Turner
2016-12-29 2:04 ` [PATCH v5 0/2] repack (oops) 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=1482965142-6778-1-git-send-email-dturner@twosigma.com \
--to=dturner@twosigma.com \
--cc=git@vger.kernel.org \
--cc=j6t@kgdb.org \
--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).