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 (Mar 2025, #02; Thu, 6)
Date: Mon, 10 Mar 2025 18:09:34 -0400 [thread overview]
Message-ID: <Z89jHhnQfRRjd1nf@nand.local> (raw)
In-Reply-To: <xmqqzfhxfym4.fsf@gitster.g>
On Thu, Mar 06, 2025 at 04:55:31PM -0800, Junio C Hamano wrote:
> * tb/multi-cruft-pack-refresh-fix (2025-03-04) 1 commit
> - builtin/pack-objects.c: freshen objects from existing cruft packs
>
> Certain "cruft" objects would have never been refreshed when there
> are multiple cruft packs in the repository, which has been
> corrected.
>
> Will merge to 'next'?
> source: <6e93471f9a8e6a3dde36342088748ba17e4f7f95.1741133712.git.me@ttaylorr.com>
Let's hold off for now, I discovered one more issue with the interaction
between --max-pack-size and --cruft in pack-objects that will be easier
to address within that series instead of on top.
Thanks,
Taylor
next prev parent reply other threads:[~2025-03-10 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 0:55 What's cooking in git.git (Mar 2025, #02; Thu, 6) Junio C Hamano
2025-03-10 22:09 ` Taylor Blau [this message]
2025-03-11 14:46 ` shejialuo
2025-03-11 17:05 ` Junio C Hamano
2025-03-12 14:09 ` shejialuo
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=Z89jHhnQfRRjd1nf@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).