git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Vicent Marti <tanoku@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Lift --stdout restriction for using reachability bitmap in pack-objects?
Date: Tue, 17 Feb 2015 05:13:44 -0500	[thread overview]
Message-ID: <20150217101344.GA5343@peff.net> (raw)
In-Reply-To: <CACsJy8AC5ZcsB2_qS4k-+6fJt2_e7m=o8C9UAEcywh=P_4HXAw@mail.gmail.com>

On Tue, Feb 17, 2015 at 05:07:36PM +0700, Duy Nguyen wrote:

> Commit 6b8fda2 (pack-objects: use bitmaps when packing objects -
> 2013-12-21) turns off reachability bitmap optimization if --stdout is
> not specified. I wonder if we could lift this restriction?

I'm not sure what else would break if we did. For instance, would
bitmaps kick in when doing the "Counting objects" phase of "git repack
-ad". And if so, what would the resulting pack look like?

So I'm not opposed to it in principle, but I suspect there's some
cleanup work to be done. But...

> My use case is debugging pack-objects in gdb (repeatedly) where this
> optimization could really save time. But specifying --stdout would
> clutter gdb interface.. I don't know this code well enough to judge,
> but I think the worst thing is we don't write .idx file out (maybe
> because it would involve a lot more work).

If the only reason is for gdb, then perhaps:

  set args pack-objects --stdout </dev/null >/dev/null

in gdb would help?

-Peff

  reply	other threads:[~2015-02-17 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 10:07 Lift --stdout restriction for using reachability bitmap in pack-objects? Duy Nguyen
2015-02-17 10:13 ` Jeff King [this message]
2015-02-17 10:36   ` Duy Nguyen
2015-02-17 10:42     ` Jeff King
2015-02-19  0:09       ` Kyle J. McKay

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=20150217101344.GA5343@peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    --cc=tanoku@gmail.com \
    /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).