From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: What's cooking in git.git (Aug 2025, #01; Sun, 3)
Date: Mon, 04 Aug 2025 07:29:23 -0700 [thread overview]
Message-ID: <xmqqqzxr88jg.fsf@gitster.g> (raw)
In-Reply-To: <aJCBlnHp-db4Nd5w@pks.im> (Patrick Steinhardt's message of "Mon, 4 Aug 2025 11:47:02 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> On Mon, Aug 04, 2025 at 01:23:40AM -0700, Junio C Hamano wrote:
>> * ps/remote-rename-fix (2025-07-31) 7 commits
>> - builtin/remote: only iterate through refs that are to be renamed
>> - builtin/remote: rework how remote refs get renamed
>> - builtin/remote: determine whether refs need renaming early on
>> - builtin/remote: fix sign comparison warnings
>> - refs: simplify logic when migrating reflog entries
>> - refs: pass refname when invoking reflog entry callback
>> - Merge branch 'ps/reflog-migrate-fixes' into ps/remote-rename-fix
>> (this branch uses ps/reflog-migrate-fixes.)
>>
>> "git remote rename origin upstream" failed to move origin/HEAD to
>> upstream/HEAD when origin/HEAD is unborn and performed other
>> renames extremely inefficiently, which has been corrected.
>>
>> Will merge to 'next'?
>> source: <20250731-pks-remote-rename-improvements-v2-0-dda6f083674d@pks.im>
>
> I've sent one more version of this patch series for a couple of final
> finishing touches. If Peff is happy with that version I'm happy to see
> it merged.
Hmph, you have?
>
>> * ps/reflog-migrate-fixes (2025-07-29) 9 commits
>> - refs: fix invalid old object IDs when migrating reflogs
>> - refs: stop unsetting REF_HAVE_OLD for log-only updates
>> - refs/files: detect race when generating reflog entry for HEAD
>> - refs: fix identity for migrated reflogs
>> - ident: fix type of string length parameter
>> - builtin/reflog: implement subcommand to write new entries
>> - refs: export `ref_transaction_update_reflog()`
>> - builtin/reflog: improve grouping of subcommands
>> - Documentation/git-reflog: convert to use synopsis type
>> (this branch is used by ps/remote-rename-fix.)
>>
>> "git refs migrate" to migrate the reflog entries from a refs
>> backend to another had a handful of bugs squashed.
>>
>> Will merge to 'next'?
>> source: <20250729-pks-reflog-append-v3-0-9614d310f073@pks.im>
>
> I'm happy with this version, so if the above goes in I think this one
> here can also be merged.
You have an update for this one. Perhaps your comments are swapped
between these two topics?
next prev parent reply other threads:[~2025-08-04 14:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 8:23 What's cooking in git.git (Aug 2025, #01; Sun, 3) Junio C Hamano
2025-08-04 9:47 ` Patrick Steinhardt
2025-08-04 14:29 ` Junio C Hamano [this message]
2025-08-04 14:51 ` Patrick Steinhardt
2025-08-04 15:41 ` Jeff King
2025-08-05 0:34 ` Junio C Hamano
2025-08-05 12:51 ` Jeff King
2025-08-05 17:08 ` Junio C Hamano
2025-08-05 18:48 ` Jeff King
2025-08-05 13:05 ` Patrick Steinhardt
2025-08-05 13:44 ` Jeff King
2025-08-05 17:10 ` Junio C Hamano
2025-08-05 1:22 ` D. Ben Knoble
2025-08-05 10:24 ` Junio C Hamano
2025-08-05 16:23 ` D. Ben Knoble
2025-08-05 16:30 ` D. Ben Knoble
2025-08-05 19:06 ` Junio C Hamano
2025-08-05 19:18 ` Ben Knoble
2025-08-06 17:28 ` Lucas Seiki Oshiro
2025-08-06 18:34 ` 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=xmqqqzxr88jg.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=ps@pks.im \
/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).