git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jonathan Tan <jonathantanmy@google.com>
Subject: Re: What's cooking in git.git (Oct 2021, #01; Mon, 4)
Date: Mon, 4 Oct 2021 19:52:57 -0400	[thread overview]
Message-ID: <YVuT2aOzcjmgX+K0@nand.local> (raw)
In-Reply-To: <xmqqo884tkxd.fsf@gitster.g>

On Mon, Oct 04, 2021 at 04:44:14PM -0700, Junio C Hamano wrote:
> * tb/aggregate-ignore-leading-whitespaces (2021-10-04) 1 commit
>  Will merge to 'next'.

Thanks for picking this one up. I definitely wrote it as a sketch, but
I think it's useful as-is, so I'm glad to see it move forward.

> * tb/repack-write-midx (2021-10-01) 9 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: rename variables that deal with non-kept packs
>  - 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
>
>  "git repack" has been taught to generate multi-pack reachability
>  bitmaps.
>
>  Will merge to 'next'?

I think so. Jonathan Tan and others gave this a thorough review. I did
send a replacement for the last patch, which you can find here:

  https://lore.kernel.org/git/YVeN0mXqYvTHtNB+@nand.local

(I realize that this is in response to v2 8/8, but it should apply as a
replacement for the final patch in the *third* version of this series.
If it's too much of a hassle, I'm happy to just send you a clean v4,
too).

Thanks,
Taylor

  reply	other threads:[~2021-10-04 23:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 23:44 What's cooking in git.git (Oct 2021, #01; Mon, 4) Junio C Hamano
2021-10-04 23:52 ` Taylor Blau [this message]
2021-10-05 16:01 ` ab/refs-errno-cleanup Ævar Arnfjörð Bjarmason
2021-10-05 16:47 ` hm/paint-hits-in-log-grep Ævar Arnfjörð Bjarmason
2021-10-05 17:07 ` ab/designated-initializers-more Ævar Arnfjörð Bjarmason
2021-10-05 20:47 ` ab/fsck-unexpected-type (and "cat-file replace handling and optimization") Ævar Arnfjörð Bjarmason
2021-10-05 22:01   ` Jeff King
2021-10-06  8:54     ` Ævar Arnfjörð Bjarmason
2021-10-07 21:37     ` Junio C Hamano
2021-10-08  2:25       ` Jeff King
2021-10-08 20:50         ` Junio C Hamano
2021-10-06 10:14 ` ab/make-sparse-for-real Ævar Arnfjörð Bjarmason
2021-10-06 10:17 ` ab/parse-options-cleanup & ab/align-parse-options-help & ab/help-config-vars Ævar Arnfjörð Bjarmason
2021-10-06 16:44   ` Junio C Hamano
2021-10-06 10:26 ` ab/refs-errno-cleanup & "errno" removal in the refs backend Ævar Arnfjörð Bjarmason

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YVuT2aOzcjmgX+K0@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jonathantanmy@google.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).