git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2021, #04; Mon, 13)
Date: Tue, 14 Sep 2021 01:43:06 -0400	[thread overview]
Message-ID: <YUA2ajsm8q2EtH9h@nand.local> (raw)
In-Reply-To: <xmqqtuinc3tx.fsf@gitster.g>

On Mon, Sep 13, 2021 at 07:02:02PM -0700, Junio C Hamano wrote:
> * tb/repack-write-midx (2021-09-10) 8 commits
>  - builtin/repack.c: pass `--refs-snapshot` when writing bitmaps
>  - builtin/repack.c: make largest pack preferred
>  - builtin/repack.c: support writing a MIDX while repacking
>  - builtin/repack.c: extract showing progress to a variable
>  - builtin/repack.c: keep track of existing packs unconditionally
>  - midx: preliminary support for `--refs-snapshot`
>  - builtin/multi-pack-index.c: support --stdin-packs mode
>  - midx: expose 'write_midx_file_only()' publicly
>  (this branch uses tb/multi-pack-bitmaps.)
>
>  "git repack" has been taught to generate multi-pack reachability
>  bitmaps.

I think that this is in a good state, although I would like to get
another review (particularly it would be good to have somebody weigh in
on the --refs-snapshot format question that Ævar raised [1]).

[1]: https://lore.kernel.org/git/87sfyb8ihg.fsf@evledraar.gmail.com/

> * tb/midx-write-propagate-namehash (2021-09-12) 4 commits
>  - t5326: test propagating hashcache values
>  - midx.c: respect 'pack.writeBitmapHashcache' when writing bitmaps
>  - pack-bitmap.c: propagate namehash values from existing bitmaps
>  - t/helper/test-bitmap.c: add 'dump-hashes' mode
>  (this branch uses tb/multi-pack-bitmaps.)
>
>  "git multi-pack-bitmap write" learns to propagate the hashcache
>  from original bitmap to resulting bitmap.

Another reroll coming, but the series is mostly unchanged (the reroll
fixes a couple of test and perf-test related bugs and adds some
performance numbers).

One small nit, s/multi-pack-bitmap write/multi-pack-index write
--bitmap/.

Thanks,
Taylor

  parent reply	other threads:[~2021-09-14  5:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14  2:02 What's cooking in git.git (Sep 2021, #04; Mon, 13) Junio C Hamano
2021-09-14  4:13 ` Elijah Newren
2021-09-14  5:43 ` Taylor Blau [this message]
2021-09-14 13:33 ` Derrick Stolee
2021-09-14 17:47   ` Junio C Hamano
2021-09-14 19:47 ` Jeff Hostetler
2021-09-14 20:51   ` Junio C Hamano
2021-09-14 20:57     ` Jeff Hostetler
2021-09-14 19:54 ` Philip Oakley

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=YUA2ajsm8q2EtH9h@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).