git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Aug 2025, #01; Sun, 3)

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 4, 2025, 14:29 UTC
Message-ID
<xmqqqzxr88jg.fsf@gitster.g>
In-Reply-To
<aJCBlnHp-db4Nd5w@pks.im>
Patrick Steinhardt <ps@pks.im> writes:
Show 21 quoted lines
> 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?
Show 21 quoted lines
>
>> * 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?

Previous: Patrick SteinhardtNext: Patrick Steinhardt
Message 3 of 20 in “What's cooking in git.git (Aug 2025, #01; Sun, 3)”
  1. Junio C HamanoAug 4, 2025
  2. Patrick SteinhardtAug 4, 2025
  3. Junio C HamanoAug 4, 2025
  4. Patrick SteinhardtAug 4, 2025
  5. Jeff KingAug 4, 2025
  6. Junio C HamanoAug 5, 2025
  7. Jeff KingAug 5, 2025
  8. Junio C HamanoAug 5, 2025
  9. Jeff KingAug 5, 2025
  10. Patrick SteinhardtAug 5, 2025
  11. Jeff KingAug 5, 2025
  12. Junio C HamanoAug 5, 2025
  13. D. Ben KnobleAug 5, 2025
  14. Junio C HamanoAug 5, 2025
  15. D. Ben KnobleAug 5, 2025
  16. D. Ben KnobleAug 5, 2025
  17. Junio C HamanoAug 5, 2025
  18. Ben KnobleAug 5, 2025
  19. Lucas Seiki OshiroAug 6, 2025
  20. Junio C HamanoAug 6, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.