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: Jeff King <peff@peff.net>, Elijah Newren <newren@gmail.com>,
	git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)
Date: Wed, 9 Jul 2025 10:46:47 -0400	[thread overview]
Message-ID: <aG6A19ZgxwpdJuow@nand.local> (raw)
In-Reply-To: <xmqqplebzgm7.fsf@gitster.g>

> * tb/midx-avoid-cruft-packs (2025-06-23) 9 commits
>  - repack: exclude cruft pack(s) from the MIDX where possible
>  - pack-objects: introduce '--stdin-packs=follow'
>  - pack-objects: swap 'show_{object,commit}_pack_hint'
>  - pack-objects: fix typo in 'show_object_pack_hint()'
>  - pack-objects: perform name-hash traversal for unpacked objects
>  - pack-objects: declare 'rev_info' for '--stdin-packs' earlier
>  - pack-objects: factor out handling '--stdin-packs'
>  - pack-objects: limit scope in 'add_object_entry_from_pack()'
>  - pack-objects: use standard option incompatibility functions
>
>  "pack-objects" has been taught to avoid pointing into objects in
>  cruft packs from midx.
>
>  Will merge to 'next'?
>  source: <cover.1750717921.git.me@ttaylorr.com>

I think that this one is ready to go. Since Elijah and Peff last
reviewed it, it hasn't changed substantially (other than a few
bugfix-related changes that were discovered while rolling this out at
GitHub).

The series has been running on GitHub's production infrastructure for
the last month or two without issue, so I think this is good from a
stability perspective.

I've CC'd Elijah and Peff here, since they were the last two to review
the series, but I don't think that they have any objections to this
moving along.

Thanks,
Taylor

  parent reply	other threads:[~2025-07-09 14:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08  0:11 What's cooking in git.git (Jul 2025, #02; Mon, 7) Junio C Hamano
2025-07-08  0:47 ` Ayush Chandekar
2025-07-09  9:25 ` René Scharfe
2025-07-09 15:37   ` Junio C Hamano
2025-07-09 10:41 ` Carlo Marcelo Arenas Belón
2025-07-09 14:15   ` Phillip Wood
2025-07-09 15:04   ` Johannes Sixt
2025-07-10  4:25     ` Carlo Marcelo Arenas Belón
2025-07-10  7:18       ` Johannes Sixt
2025-07-10 15:30         ` Junio C Hamano
2025-07-09 16:26   ` Junio C Hamano
2025-07-09 14:46 ` Taylor Blau [this message]
2025-07-10  0:01   ` Junio C Hamano
2025-07-10  1:05     ` Elijah Newren
2025-07-10  4:24       ` Junio C Hamano
2025-07-09 23:14 ` brian m. carlson
2025-07-10  4:24   ` Junio C Hamano

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