Here are the topics that have been cooking in my tree. Commits prefixed with '+' are in 'next' (being in 'next' is a sign that a topic is stable enough to be used and is a candidate to be in a future release). Commits prefixed with '-' are only in 'seen', and aren't considered "accepted" at all. They may be annotated with a URL to a message that raises issues but they are by no means exhaustive. A topic without enough support may be discarded after a long period of no activity (of course, it can be resubmitted when new interest arises). The 16th batch of topics have now graduated to the 'master' branch. We have 472 non-merge commits in 'master' since Git 2.55. There are 128 non-merge commits cooking in 'next' (note that some have been reverted), and 245 non-merge commits, including those in and out of 'next', in 'seen' as of this writing. Copies of the source code to Git live in many repositories, and the following is a list of the ones I push into or their mirrors. Some repositories have only a subset of branches. With maint, master, next, seen, todo: git://git.kernel.org/pub/scm/git/git.git/ git://repo.or.cz/alt-git.git/ https://kernel.googlesource.com/pub/scm/git/git/ https://github.com/git/git/ https://gitlab.com/git-scm/git/ With all the integration branches and topics broken out: https://github.com/gitster/git/ Even though the preformatted documentation in HTML and man format are not sources, they are published in these repositories for convenience (replace "htmldocs" with "manpages" for the manual pages): git://git.kernel.org/pub/scm/git/git-htmldocs.git/ https://github.com/gitster/git-htmldocs.git/ Release tarballs are available at: https://www.kernel.org/pub/software/scm/git/ -------------------------------------------------- [New Topics] * kn/receive-report-hook (2026年08月18日) 1 commit - hook: introduce the report hook for git-receive-pack(1) A new hook 'report' is added to 'git receive-pack', which runs after reference updates and allows the server to filter or modify the packet-line status report sent back to the client. Expecting a reroll. cf. <CAOLa=ZSuzd3FozharJ_1LRgaQdpY+eRZnMOJYoLJNvPXiait1w@xxxxxxxxxxxxxx> source: <20260818-758-introduce-hook-v1-1-8a8d89e65838@xxxxxxxxx> * en/midx-missing-pack-fallback (2026年08月18日) 2 commits - packfile: recover when a multi-pack-index names a removed pack - replay: fail gracefully when a merge input is unreadable The object lookup machinery has been taught to gracefully recover when a multi-pack-index points to an owning pack that was removed during a concurrent geometric repack, and 'git replay' has been fixed to not segfault when reading such missing objects. Waiting for response. cf. <xmqqfr0augls.fsf@gitster.g> cf. <aoayppoxHAkcFTBN@xxxxxx> source: <pull.2207.git.1787092446.gitgitgadget@xxxxxxxxx> * ll/zsh-complete-git-potty-options (2026年08月19日) 1 commit - completion: zsh: support completion after "git -C <path>" The zsh completion script (in 'contrib/') has been updated to correctly locate the Git command after global options like '-C' by properly skipping them, similar to how the bash completion does. Needs review. cf. <CALnO6CC35iuyJpKZtkEN7fGuGK7zKd_jbebyZdKSQ1pyfOBRZA@xxxxxxxxxxxxxx> source: <pull.2155.v2.git.1787144872870.gitgitgadget@xxxxxxxxx> * ps/odb-generic-corrupt-objects (2026年08月19日) 5 commits - odb: handle `OBJECT_INFO_DIE_IF_CORRUPT` generically - odb/source: allow `read_object_info()` to bubble up error messages - odb/source: let callers discern missing and corrupt objects - odb/source: introduce error status when reading objects - odb/source-packed: flag known-bad objects as corrupt and not missing The object database (odb) API has been refactored to distinguish between missing objects and corrupt ones by returning more descriptive error statuses. Both the packed and loose backends now faithfully propagate error details using a generic strbuf error mechanism, removing backend-specific leakage from central lookup paths. Waiting for review. cf. <CAOLa=ZTVxdVAJynKjb0LjmZ-+b5nQmyD0Bm-aT81rOOdJ0a5yg@xxxxxxxxxxxxxx> cf. <aocNsR60-8W2A-fy@xxxxxx> cf. <aocNq1N9MWS4BeaJ@xxxxxx> source: <20260819-pks-odb-generic-corrupt-objects-v2-0-a984e3a0ad6f@xxxxxx> * ap/http-preserve-wwwauth-redirect (2026年08月19日) 1 commit - http: preserve wwwauth_headers across redirects When an HTTP request triggers a redirect and the target yields an authentication challenge, the WWW-Authenticate headers received during the redirect are now explicitly preserved across the credential URL update, fixing an issue where they were incorrectly cleared. Needs review. source: <20260819-http-preserve-wwwauth-redirect-v2-1-4c61039432b0@xxxxxxxxxx> * fr/pack-objects-trace-pack-bytes (2026年08月19日) 1 commit - pack-objects: trace pack bytes written The pack-objects command has been updated to record the total bytes written to pack files in trace2 output, allowing performance analysis of different compression settings by comparing the resulting pack sizes. Needs review. cf. <aobFLJuiuM1EuNpv@xxxxxx> cf. <20260820082102.GA2973952@xxxxxxxxxxxxxxxxxxxxxxx> source: <c6a8cdac36d2202055d637ebcc97e484122cdcd4.1787158152.git.friel@xxxxxxxxxx> * kh/doc-datamodel (2026年08月20日) 4 commits - doc: datamodel: link to the glossary - doc: glossary: link four of the terms to gitdatamodel(7) - doc: git: link to the gitdatamodel(7) tutorial - doc: git: list gitdatamodel(7) as a concept guide The gitdatamodel documentation page has been linked from a handful of key documentaiton pages. Needs review. source: <CV_doc_datamodel_advertize.bea@xxxxxxxxx> * yn/worktree-repair-relative (2026年08月20日) 1 commit - worktree repair: detect relative path in .git file correctly The git worktree repair command failed to rewrite the .git file of a working tree from a relative path to an absolute path when the command was run in the working tree itself. The read_gitfile_gently() function was modified to also return whether the path originally recorded in the file was absolute, and this new capability is used to correctly detect such mismatches. Needs review. source: <pull.2205.v2.git.1787240760069.gitgitgadget@xxxxxxxxx> -------------------------------------------------- [Graduated to 'master'] * hn/bisect-reset-when-found (2026年08月02日) 2 commits (merged to 'next' on 2026年08月11日 at cad4ed37c6) + bisect: add --reset-when-found to leave when done + bisect: let bisect_reset() optionally check out quietly The 'git bisect' command has been taught a '--reset-when-found[=<where>]' option that tells the command to automatically run 'git bisect reset' to jump back to the original state or to the found culprit. Graduated to 'master'. cf. <xmqqldajjgn3.fsf@gitster.g> source: <pull.2335.v6.git.git.1785705860.gitgitgadget@xxxxxxxxx> * hn/branch-delete-merged (2026年08月05日) 7 commits (merged to 'next' on 2026年08月13日 at 07f0138e2e) + branch: add --dry-run for --delete-merged + branch: add branch.<name>.deleteMerged opt-out + branch: add --delete-merged <pattern> + branch: prepare delete_branches for a bulk caller + branch: let delete_branches skip unmerged branches on bulk refusal + branch: convert delete_branches() to a flags argument + branch: add --forked filter for --list mode The 'git branch' command has been taught the '--delete-merged' option to remove local branches that are already merged into their tracked remote-tracking branches. Graduated to 'master'. cf. <10b22a6b-e028-469c-a117-8dc2ed5bed3b@xxxxxxxxx> source: <pull.2285.v25.git.git.1785939877.gitgitgadget@xxxxxxxxx> * kh/doc-refs-migrate-limitations (2026年08月05日) 2 commits (merged to 'next' on 2026年08月11日 at 2eb1041920) + doc: refs: linkgit to git-maintenance(1) + doc: refs: put ref migration warning under the command The known limitations of the ref format migration in 'git refs' have been moved to be displayed as a warning admonition directly under the description of the 'migrate' subcommand, improving visibility. A reference to 'git-maintenance' has also been corrected to use the 'linkgit' macro. Graduated to 'master'. cf. <anQYWlv3UhpS3iE7@xxxxxx> cf. <CAOLa=ZQQnrRca60BAfnm6Azu=bHvnoVhcGwQ3KkDT7yqLDd8Dw@xxxxxxxxxxxxxx> source: <V3_CV_git_ref_migration_warning.b23@xxxxxxxxx> * kh/doc-trailers (2026年08月09日) 11 commits (merged to 'next' on 2026年08月13日 at 2966f0265a) + doc: interpret-trailers: document comment line treatment + doc: interpret-trailers: rewrite new-trailers paragraphs + doc: interpret-trailers: commit to “trailer block” term + doc: interpret-trailers: join new-trailers again + doc: interpret-trailers: add key format example + doc: interpret-trailers: explain key format + doc: interpret-trailers: explain the format after the intro + doc: interpret-trailers: not just for commit messages + doc: interpret-trailers: use “metadata” in Name as well + doc: interpret-trailers: replace “lines” with “metadata” + doc: interpret-trailers: stop fixating on RFC 822 (this branch is used by kh/trailers-no-urls.) Documentation for 'git interpret-trailers' has been updated to explain the format of trailer keys (alphanumeric characters and hyphens), replace outdated terminology, define key terms upfront, and document how comment lines in the input are treated. Graduated to 'master'. cf. <0687D60D-DF6B-4547-868C-FCFC5B27ECAF@xxxxxxxxx> source: <V5_CV_doc_int-tr_key_format.b26@xxxxxxxxx> * ps/odb-make-creation-pluggable (2026年08月06日) 6 commits (merged to 'next' on 2026年08月13日 at 749fa77ae1) + odb: make creation of on-disk structures pluggable + odb/source: introduce function to map source type to name + setup: defer object database creation + setup: handle ODB-related environment variables in `odb_new()` + setup: detangle loading of loose object maps + loose: load loose object map for the correct source (this branch is used by ps/odb-eagerly-load-alternates.) The creation of the on-disk data structures for the object database has been made pluggable, allowing future backends to customize their setup. As part of this, the initialization of the object database has been deferred, and the loading of the loose-object map has been detangled from repository initialization. Graduated to 'master'. cf. <87jyq24cxm.fsf@xxxxxxxxxxxxxxx> source: <20260807-pks-odb-create-on-disk-v5-0-399da0b0b140@xxxxxx> * ps/writev (2026年08月06日) 5 commits (merged to 'next' on 2026年08月11日 at bc2a935c92) + fast-import: use writev(3p) to send cat-blob responses + sideband: use writev(3p) to send pktlines + wrapper: properly handle MAX_IO_SIZE in writev(3p) + wrapper: introduce writev(3p) wrappers + compat/posix: introduce writev(3p) wrapper A compatibility wrapper for writev(3p) has been reintroduced, including fixes for CMake build and 'MAX_IO_SIZE' limits on NonStop. Calls to write(3p) in send_sideband() and cat_blob() have been refactored to use writev(3p) wrappers to reduce syscall overhead. Graduated to 'master'. cf. <xmqqcxvvhu6q.fsf@gitster.g> source: <20260807-pks-reintroduce-writev-v2-0-30fcff0e89c1@xxxxxx> -------------------------------------------------- [Stalled] * hs/rebase-continue-edit (2026年07月21日) 1 commit - rebase: add --[no-]edit to --continue Support for skipping the editor when continuing a rebase after conflict resolution has been added with the '--no-edit' option, and forcing it with '--edit'. A new configuration variable 'rebase.noEdit' can be used to set the default behavior. Waiting for response for too long, stalled. cf. <xmqqldb4xlqa.fsf@gitster.g> cf. <db7edc66-9b2a-47bc-98db-87d01885cef0@xxxxxxxxx> source: <20260721140443.1809379-2-hugo@xxxxxxx> -------------------------------------------------- [Cooking] * sk/object-name-use-after-free (2026年08月17日) 1 commit (merged to 'next' on 2026年08月20日 at b0804dff5f) + object-name: avoid use-after-free in get_oid_with_context_1() A heap-use-after-free bug in the object name parsing code when reporting failures with a relative path to a sparse directory has been corrected. Will merge to 'master'. cf. <xmqq1pbw7nwi.fsf@gitster.g> source: <20260817082127.81132-1-diy2903@xxxxxxxxx> * kh/format-rev-doc-synopsis (2026年08月17日) 2 commits (merged to 'next' on 2026年08月20日 at b9c47eddd0) + doc: format-rev: use [synopsis] on code block + doc: format-rev: quote subject placeholder before and after The documentation for 'git format-rev' has been updated to use the [synopsis] block definition on code blocks to properly highlight placeholders, and a quoting inconsistency in the running text has been fixed. Will merge to 'master'. cf. <xmqq33wc4dyq.fsf@gitster.g> source: <V4_CV_synopsis_block.b8e@xxxxxxxxx> * kh/format-rev-more-options (2026年08月18日) 5 commits - format-rev: learn --abbrev, --color, and --date - doc: rev-list-options.adoc: factor out --date alts - format-rev: factor option variables into a struct - format-rev: place BUG calls first in callback - format-rev: use lower case for opts description The experimental 'git format-rev' has been taught a few more formatting options. Needs review. source: <V2_CV_format-rev_three_more_opts.bd3@xxxxxxxxx> * ps/odb-pluggable-pack-generation (2026年08月20日) 6 commits - bundle: generate packfiles via the object database - bundle: get (mostly) rid of `the_repository` - builtin/bundle: refactor option handling for progress meter - send-pack: generate packfiles via the object database - upload-pack: generate packfiles via the object database - odb: introduce interface to generate packfiles The mechanism to generate a packfile corresponding to the result of a fetch/push has been made pluggable through a set of object database callback functions, removing hardcoded references to 'pack-objects' and enabling alternative ODBs to serve packfiles themselves. Expecting a reroll. cf. <aobnos_v8xko0w57@xxxxxx> source: <20260820-b4-pks-odb-generate-pack-v3-0-bc42252f6169@xxxxxx> * ty/repository-fetch-if-missing (2026年08月14日) 1 commit - repository: move fetch_if_missing into struct repository The global variable 'fetch_if_missing' has been moved to a member in 'struct repository', continuing the libification process and allowing per-repository control (such as for submodules). Will merge to 'next'? cf. <xmqqmrun8jeu.fsf@gitster.g> source: <20260815064747.2196896-1-cat@xxxxxxxxx> * ns/ref-symref-additional-tests (2026年08月13日) 2 commits - t1401: test symbolic-ref exit codes on a non-symbolic ref - t1402: test forbidden characters in refnames A few additional tests. Expecting a reroll. cf. <20260820151325.58087-1-nikolauspschuetz@xxxxxxxxx> cf. <20260820144648.47267-1-nikolauspschuetz@xxxxxxxxx> source: <pull.2204.git.1786655554197.gitgitgadget@xxxxxxxxx> source: <pull.2203.git.1786653837190.gitgitgadget@xxxxxxxxx> * en/diff-l-opt-help (2026年08月13日) 1 commit (merged to 'next' on 2026年08月17日 at 4b6b3295ed) + diff: avoid misleading statement about -l option The help text for the '-l' option of 'git diff' has been updated. Will merge to 'master'. cf. <xmqqbjb4rd5q.fsf@gitster.g> source: <pull.2035.v2.git.1786673186855.gitgitgadget@xxxxxxxxx> * ss/submittingpatches-typofix (2026年08月14日) 1 commit (merged to 'next' on 2026年08月18日 at b251ddc3d7) + doc: fix typo in submitting patches Typofix. Will merge to 'master'. cf. <xmqq7blsmru5.fsf@gitster.g> source: <pull.2383.git.git.1786733219160.gitgitgadget@xxxxxxxxx> * ch/chdir-notify-drop-name (2026年08月14日) 1 commit (merged to 'next' on 2026年08月18日 at 973cefddd7) + chdir-notify.h: Removed unused param 'name' The unused name parameter in 'struct chdir_notify_entry' has been removed from chdir_notify_register(), chdir_notify_unregister(), and related callback signatures across several subsystems, simplifying the API now that trace output no longer uses it. Will merge to 'master'. cf. <20260815051213.GA26013@xxxxxxxxxxxxxxxxxxxxxxx> source: <20260814214210.1625-1-colinlewishinton@xxxxxxxxx> * cc/git-shallow-file-wo-value (2026年08月11日) 1 commit (merged to 'next' on 2026年08月17日 at f6a6ff92a6) + git: avoid segfault on "git --shallow-file" without a value The '--shallow-file' option of 'git' command requires a value, but the code did not check the presence of a value and instead segfaulted without one, which has been corrected. Will merge to 'master'. cf. <an10XhFPo0nJWJIV@xxxxxx> cf. <xmqqcxvo1n8w.fsf@gitster.g> source: <20260811121446.2080190-1-christian.couder@xxxxxxxxx> * js/sequencer-release-odb-before-commit (2026年08月12日) 1 commit (merged to 'next' on 2026年08月15日 at 1c83dffd7a) + sequencer: release the ODB before spawning git commit The sequencer has been updated to release the object database before spawning 'git commit'. This prevents open file handles from blocking auto-maintenance tasks, such as repacking, on systems like Windows where open files cannot be easily unlinked. Will merge to 'master'. cf. <xmqqqzk3xqxs.fsf@gitster.g> source: <pull.2198.v2.git.1786528498689.gitgitgadget@xxxxxxxxx> * jt/receive-pack-pluggable-writes (2026年08月19日) 9 commits - odb/transaction: add transaction interface to write packfiles - odb: return temporary ODB source when set - builtin/receive-pack: explicitly pass packfile fd - builtin/receive-pack: report unpack errors via strbuf - builtin/receive-pack: lift global state out of unpack() - builtin/receive-pack: read unpack limit config lazily - builtin/receive-pack: pass shallow file explicitly - odb/transaction: add transaction finalize interface - builtin/receive-pack: properly clean up keep files The 'git receive-pack' command has been updated to use a new ODB transaction interface for writing incoming packfiles, making it more backend-agnostic. Expecting a reroll. cf. <aodyeILDMaBOX--K@denethor> cf. <aoaiz7M1oGboydY4@xxxxxx> cf. <aoaiy1wmSXjL30-m@xxxxxx> cf. <aoaixMF1biKYhWN2@xxxxxx> source: <20260819215311.3880274-1-jltobler@xxxxxxxxx> * jc/complete-checkout (2026年08月13日) 4 commits (merged to 'next' on 2026年08月19日 at 758fc8c411) + completion: 'git checkout' completes untracked paths as a last resort + completion: complete tracked paths for "git checkout" + completion: no-op refactoring of checkout completion + Merge branch 'jc/complete-diff-tracked-paths' into jc/complete-checkout (this branch uses jc/complete-diff-tracked-paths.) Will merge to 'master'. cf. <CABPp-BFeLStBR3OeTCJoBmC7cn_VXrn4RcvBg-WWGyz4LpJxsg@xxxxxxxxxxxxxx> source: <20260813191234.1066662-1-gitster@xxxxxxxxx> * en/sequencer-lose-pretty-given (2026年08月11日) 1 commit (merged to 'next' on 2026年08月17日 at 82d0706aef) + sequencer: remove unnecessary variable setting The setting of a now-unused member '.pretty_given' in the sequencer machinery has been removed. Will merge to 'master'. cf. <an11zsTm-fanH8yt@xxxxxx> cf. <xmqqa4qrxneq.fsf@gitster.g> source: <pull.1922.git.1786516959130.gitgitgadget@xxxxxxxxx> * en/serve-promisor-remote-fix (2026年08月11日) 1 commit (merged to 'next' on 2026年08月17日 at a4d7a9d1d6) + serve: reject valueless promisor-remote capability A client requesting the promisor-remote capability without a value caused a null pointer dereference, which has been corrected by rejecting a request without an argument. Will merge to 'master'. cf. <CAP8UFD0+iXC3VxWmuuuB7La-pP6hdz58tr6vaEJSKpXJ_4ZH2w@xxxxxxxxxxxxxx> source: <pull.2199.git.1786516783909.gitgitgadget@xxxxxxxxx> * ps/odb-eagerly-load-alternates (2026年08月17日) 6 commits - odb: drop `alternates_db` field - odb: drop `loaded_alternates` field - odb: eagerly initialize alternates - odb: decouple source path comparisons from `the_repository` - setup: create ref and object databases after config is written - Merge branch 'ps/odb-make-creation-pluggable' into ps/odb-eagerly-load-alternates The object database layer has been simplified by eagerly loading alternate object directories upon initialization, instead of deferring it to the first object lookup. This eliminates the need for scattered lazy-loading calls throughout the codebase and paves the way for integrating alternates with the pluggable backends. Waiting for response. cf. <an36BA_Nw7eLAKYC@denethor> cf. <CAOLa=ZT-ObRJ3t0XYAkL33CPDZ2ULu_5M7c477rr0pZBqTBi9w@xxxxxxxxxxxxxx> cf. <xmqqmrugsryl.fsf@gitster.g> source: <20260817-pks-odb-eagerly-prepare-alternates-v3-0-1115a7e02467@xxxxxx> * gg/http-ssl-verify-status (2026年08月18日) 1 commit - http: add http.sslVerifyStatus to check stapled OCSP responses The HTTP transport has been taught to check the revocation status of the server certificate using the stapled OCSP response during the TLS handshake via a new 'http.sslVerifyStatus' configuration variable. Needs review. source: <20260818214858.65122-1-ggordon@xxxxxxxxxx> * js/packfile-fast-append (2026年08月13日) 1 commit (merged to 'next' on 2026年08月18日 at cc3da5a03d) + packfile: fix perf regression with many packs The performance of adding numerous new packfiles has been improved by introducing a fast path for known-new packfiles to skip an unnecessary traversal in packfile_list_append(), avoiding a quadratic complexity regression on load. Will merge to 'master'. cf. <an7ItVYrKZFXg2ci@xxxxxx> cf. <xmqqy0e8pxos.fsf@gitster.g> source: <pull.2202.v2.git.1786633010179.gitgitgadget@xxxxxxxxx> * hn/send-email-missing-subject-error (2026年08月10日) 1 commit (merged to 'next' on 2026年08月15日 at 6470901400) + send-email: clarify missing subject error The error message given by 'git send-email' when a message file is missing a 'Subject:' header has been clarified, and the error string is now terminated with a newline so that Perl avoids appending its internal source location data. Will merge to 'master'. cf. <xmqqtsp165tj.fsf@gitster.g> source: <pull.2375.v2.git.git.1786384412423.gitgitgadget@xxxxxxxxx> * ss/repack-drop-filtered (2026年08月13日) 6 commits (merged to 'next' on 2026年08月18日 at 23ad3f2b76) + builtin/repack: add guards for --drop-filtered + builtin/repack: actually drop filtered promisor blobs + builtin/repack: enumerate promisor blobs for --drop-filtered + repack-promisor: allow excluding objects from the rebuilt promisor pack + list-objects-filter: add list_objects_filter__filter_oidset() + builtin/repack: add --drop-filtered and --dry-run options 'git repack' has been taught '--drop-filtered' to delete local promisor blobs exceeding a limit (currently 'blob:limit=') in partial clones, reclaiming space. Guards prevent running during other operations or if referenced by the index. Will merge to 'master'. cf. <CAP8UFD1esJ0fk3xPXvAmQhMK_5wrpGKZJg9YaFV0-qUAC7bf5g@xxxxxxxxxxxxxx> source: <20260813200830.84348-1-r.siddharth.shrimali@xxxxxxxxx> * ty/repo-config-cleanups (2026年08月07日) 3 commits - environment: remove inaccurate repo_config_values comments - environment: clarify repository config getter documentation - environment: drop redundant NULL checks in config getters Repository configuration getters in 'environment.c' have been simplified by removing redundant NULL checks. The documentation for these getters in 'environment.h' has been clarified, and inaccurate section comments inside 'struct repo_config_values' have been removed. Needs review. cf. <anW7wHfUxYj9cj0P@xxxxxx> source: <20260807085932.3958759-1-cat@xxxxxxxxx> * vm/complete-history (2026年08月13日) 4 commits - completion: complete 'git history split' pathspecs - completion: complete 'git history --update-refs' values - completion: complete 'git history --empty' values - completion: add 'git history' subcommands The command line completion (in contrib/) has been taught to handle the experimental 'git history' command. Will merge to 'next'? cf. <aoWP3TYq5rNjUx7S@xxxxxx> source: <20260813-history_autocompletion-v3-0-69eed1cea93a@xxxxxxxxxx> * cc/lazy-fetch-trusted-bit (2026年08月13日) 5 commits - builtin/upload-pack: set GIT_NO_LAZY_FETCH to 0 on trusted repo - upload-pack: read uploadpack.lazyFetchTrusted - setup: add 'allow_dot' arg to path_allowlist_apply() - setup: extract path_allowlist_apply() - promisor-remote: factor out lazy_fetch_objects() A new 'uploadpack.lazyFetchTrusted' configuration variable has been introduced to allow 'upload-pack' to lazily fetch missing objects from configured promisor remotes when serving trusted repositories. Waiting for response. cf. <xmqq1pc0mr5i.fsf@gitster.g> cf. <xmqqecg0oabe.fsf@gitster.g> cf. <xmqqy0e8mv0k.fsf@gitster.g> cf. <xmqqjypsoami.fsf@gitster.g> cf. <xmqq1pc0mr5i.fsf@gitster.g> source: <20260813154748.2378747-1-christian.couder@xxxxxxxxx> * dk/use-nsec-runtime (2026年08月20日) 3 commits - core: convert build-time USE_NSEC into runtime core.useNanosec - environment: align repo_config_values_init with struct declaration - meson: expose knob for xmlto relative links in manuals The build-time knob 'USE_NSEC' for nanosecond stat precision has been converted to a runtime configuration 'core.useNanosec', allowing distributions to bundle one binary that adapts to filesystem capabilities dynamically. Needs review. cf. <xmqqa4qgsn20.fsf@gitster.g> source: <cover.1787231825.git.ben.knoble@xxxxxxxxx> * ps/t7900-deflake-maintenance (2026年08月12日) 2 commits (merged to 'next' on 2026年08月17日 at 7ef446fd59) + t7900: fix flaky "maintenance.strategy" test + t7900: adapt some tests to use a throwaway repository Various tests in 't7900-maintenance.sh' have been updated to use a throwaway repository, and auto-detaching of maintenance tasks is now disabled for these tests to fix flaky races with concurrent background maintenance jobs. Will merge to 'master'. cf. <CAOLa=ZQmZ0spmdPOzCZe36i24nQh+o7d4fSz5dcJS7+O3p2skg@xxxxxxxxxxxxxx> source: <20260812-pks-t7900-fix-flaky-test-v2-0-9ea0e1ac0edd@xxxxxx> * ps/odb-streams (2026年08月05日) 8 commits (merged to 'next' on 2026年08月15日 at a8fbd74d00) + odb/streaming: unify function names to create new streams + odb/streaming: rename `struct input_zstream_data` + odb/streaming: rename `struct read_object_fd_data` + odb/streaming: consolidate read and write streams + odb/streaming: rename `struct odb_read_stream` + odb/streaming: support streaming arbitrary object types + odb/streaming: drop `is_finished` field + odb/streaming: track write stream size in the structure The 'struct odb_read_stream' and 'struct odb_write_stream' structures have been consolidated into a single unified 'struct odb_stream' structure, simplifying object database streaming APIs and enabling streaming of arbitrary object types. Will merge to 'master'. cf. <anuBdm29ye_qV_Rq@denethor> source: <20260805-pks-odb-stream-unification-v2-0-b8c369564641@xxxxxx> * bc/restrict-hex-to-lowercase (2026年07月29日) 6 commits - hex: allow only lowercase object IDs in breaking changes mode - object-name: use hexval - hex: label usages of hex parsing for object IDs - hex: make hex_to_bytes accept kind of hex to use - hex: allow specifying hex type with hex2chr - hex: add functionality for lowercase-only hex The parser for hex object names has been updated to reject uppercase hexadecimal characters when running in the breaking changes mode, in preparation for Git 3.0. Waiting for review. cf. <anJdvLV7-raJK67B@xxxxxxxxxxxxxxxxxxxxxxxxxx> source: <20260729233215.398654-1-sandals@xxxxxxxxxxxxxxxxxxxx> * js/mingw-build-updates (2026年08月12日) 12 commits - mingw: allow `git.exe` to be used instead of the "Git wrapper" - mingw: ensure valid CTYPE - mingw: always define `ETC_*` for MSYS2 environments - windows: skip linking `git-<command>` for built-ins - mingw: rely on MSYS2's metadata instead of hard-coding it - mingw: only enable the MSYS2-specific stuff when compiling in MSYS2 - mingw: set the prefix and HOST_CPU as per MSYS2's settings - mingw: avoid over-specifying `--pic-executable` - mingw: only use -Wl,--large-address-aware for 32-bit builds - mingw: drop the -D_USE_32BIT_TIME_T option - mingw: stop hard-coding `CC = gcc` - mingw: include the Python parts in the build A collection of patches from Git for Windows has been upstreamed, mostly focusing on simplifying and robustifying build configurations for MinGW/MSYS2, dropping obsolete compatibility options, and allowing the main 'git.exe' to be used directly without the extra wrapper process on Windows. Waiting for response. cf. <4f4129df-681f-4e99-8b1f-8bb96e206a2d@xxxxxxxx> source: <pull.2195.v2.git.1786521173.gitgitgadget@xxxxxxxxx> * yn/worktree-add-no-dwim-with-b (2026年08月20日) 1 commit - worktree add: shouldn't dwim if -b or -B is given The DWIM logic in 'git worktree add' sometimes tried to infer a remote-tracking branch when an explicit '-b' or '-B' option was given to create a new branch, causing the explicit branch name to be ignored, which has been corrected. Will merge to 'next'? cf. <xmqqecfssnk0.fsf@gitster.g> source: <pull.2192.v4.git.1787221888406.gitgitgadget@xxxxxxxxx> * yn/worktree-ambiguous-remote-advice (2026年08月20日) 3 commits - worktree add: improve message for ambiguous remote branch name - checkout: improve message for ambiguous remote branch name - checkout: extract function to display advice for ambiguous remotes 'git worktree add' did not prevent DWIM behavior when '-b' or '-B' was specified, which has been corrected. Needs review. source: <pull.2197.v6.git.1787259838.gitgitgadget@xxxxxxxxx> * hn/ci-cancel-stale-pr-runs (2026年07月31日) 1 commit - ci: cancel stale pull request workflow runs GitHub Actions CI workflow runs triggered by pull requests have been configured to cancel older runs when a new push is made to the same pull request. Needs review. source: <pull.2369.git.git.1785492641983.gitgitgadget@xxxxxxxxx> * jc/complete-diff-tracked-paths (2026年08月12日) 3 commits (merged to 'next' on 2026年08月19日 at 37263f6528) + completion: 'git diff' completes untracked paths as a last resort + completion: complete tracked paths for 'git diff' + completion: no-op refactoring of diff completion (this branch is used by jc/complete-checkout.) 'git -C <dir> diff fi<TAB>' did not complete 'dir/file', which has been corrected. Will merge to 'master'. cf. <CABPp-BFdwxTvkcWKNP0-Lk+mqQLnULoYuLHZe0aot4VYfHnjSw@xxxxxxxxxxxxxx> source: <20260812162551.2229680-1-gitster@xxxxxxxxx> * kh/trailers-no-urls (2026年08月20日) 2 commits - trailers: stop recognizing URLs as trailers - Merge branch 'kh/doc-trailers' into kh/trailers-no-urls The trailers code has been taught to avoid mistaking a line that has '<token>://' at the beginning as a trailer line. Needs review. source: <V2_URLs_not_trailers.bf3@xxxxxxxxx> * cl/regexec-macos-leak (2026年07月28日) 2 commits - SQUASH??? - regexec: work around macOS TRE leak on invalid UTF-8 A compatibility workaround has been introduced for macOS to address a memory leak in the system regex engine when it encounters invalid multibyte sequences. The workaround segments the input buffer at invalid byte boundaries and searches each valid segment separately using regexec(), avoiding the leaking path. Waiting for response. cf. <xmqqse52bpa9.fsf@gitster.g> cf. <anL7qL2-4h8ZlLcg@xxxxxx> source: <20260728052538.12429-1-chungmin@xxxxxxxxxxxxxxx> * hn/checkout-m-autostash-refine (2026年07月25日) 2 commits - checkout -m: refine autostash fallback - sequencer: teach autostash apply to report conflicts The autostash fallback in 'git checkout -m' has been refined to only retry when there are local changes. Additionally, a blank line now visually separates autostash conflict advice from the subsequent branch-switch message. Needs review. cf. <xmqqwluebuhb.fsf@gitster.g> source: <pull.2364.git.git.1784993669.gitgitgadget@xxxxxxxxx> * tb/pack-with-duplicates (2026年07月24日) 5 commits - pack-bitmap: handle duplicate pack entries during MIDX reuse - test-tool bitmap: reject packs with duplicate objects - midx: verify duplicate pack entries by OID and offset - packfile: recover delta cycles through duplicate entries - t5308: test reverse indexes with duplicate objects The handling of packfiles with duplicate object entries has been hardened. Specifically, reverse index lookup, delta cycle recovery, multi-pack-index verification, and pack reuse paths have been updated to correctly handle or gracefully reject duplicate entries. Waiting for response. cf. <xmqqecgs3vg6.fsf@gitster.g> source: <cover.1784927134.git.ttaylorr@xxxxxxxxxx> * ps/cat-file-remote-object-info-type (2026年08月07日) 11 commits (merged to 'next' on 2026年08月15日 at 3f5daf59a8) + cat-file: unify default format + serve: advertise type capability + fetch-object-info: parse type from server response + protocol-caps: add type support to object-info + transport: drop remote object-info fields from transport struct + fetch-object-info: die() on the remaining error path + fetch-object-info: use dedicated struct for the results + fetch-object-info: pass arguments directly instead of a struct + fetch-object-info: detect malformed server responses + t5701: use test_file_size() to get the size of a file + Merge branch 'ps/cat-file-remote-object-info' into ps/cat-file-remote-object-info-type The 'remote-object-info' command for 'git cat-file --batch-command' has been extended to support the '%(objecttype)' placeholder. Will merge to 'master'. cf. <20260808074157.GA2915582@xxxxxxxxxxxxxxxxxxxxxxx> cf. <CA+J6zkR5ZkUc8c=xiXgKiAYmbgcoyGfwpgm6aaG0Gog8OVmOjw@xxxxxxxxxxxxxx> cf. <CAOLa=ZTrf_WHiRHTjBGAus+YbRsUkbR3dzsW=fgCK0jit6fYzQ@xxxxxxxxxxxxxx> source: <20260808-objecttype-support-v6-0-e5cdaf27a49c@xxxxxxxxx> * sn/rebase-update-refs-symrefs (2026年07月22日) 2 commits - rebase: guard non-branch symref targets - rebase: skip branch symref aliases 'git rebase --update-refs' has been taught to resolve local branch symrefs to their referents before queuing updates, ensuring aliases of the current branch are skipped and duplicate updates are avoided to prevent failures when branch aliases are present. Waiting for response, stalled. cf. <1eba5fb2-ab76-41e9-955d-e283256ad25d@xxxxxxxxx> cf. <98682fa4-55d9-4829-97f1-02e244b35266@xxxxxxxxx> source: <pull.2126.v3.git.1784708107.gitgitgadget@xxxxxxxxx> * kj/repo-info-more-path-keys (2026年08月06日) 7 commits - repo: remove unused setup.h include - repo: add path.git-prefix - repo: add path.grafts with absolute and relative suffixes - repo: add path.index with absolute and relative suffixes - repo: add path.hooks with absolute and relative suffixes - repo: add path.superproject-root with absolute and relative suffixes - repo: add path.toplevel with absolute and relative suffix formatting The 'git repo info' command has been taught more keys to output paths of various repository components (such as the working tree root, superproject working tree, object database, etc.), supporting both absolute and relative path formats. Waiting for response. cf. <6E2B0ADE-2101-47AC-B11B-315897AC2AF9@xxxxxxxxx> cf. <xmqqlda3z773.fsf@gitster.g> source: <20260806101556.162940-1-jayatheerthkulkarni2005@xxxxxxxxx> * tc/last-modified-bloom (2026年08月07日) 6 commits - last-modified: keep per-path Bloom filters for wildcard pathspecs - last-modified: check pathspec against Bloom filter first - revision: add Bloom check that includes parent directories - bloom: add helper to check if any key in a vector is present - revision: expose check for paths maybe changed in Bloom filter - revision: move bloom keyvec precondition into function The 'git last-modified' command has been optimized by using Bloom filters. It now reuses revision walk filtering logic from 'git log' to pre-filter commits, and maintains per-path Bloom filters even when wildcard pathspecs are used. Waiting for response. cf. <xmqqtsp4a6c2.fsf@gitster.g> source: <20260807-toon-speed-up-last-modified-v2-0-7d87bbdeaf9b@xxxxxxxxx> * js/coverity-unchecked-returns-fix (2026年08月12日) 12 commits (merged to 'next' on 2026年08月17日 at 105f002870) + bisect: handle dup() failure when redirecting stdout + bisect: check get_terms return at all call sites + bisect: check strbuf_getline_lf return when reading terms + transport-helper: warn when export-marks file cannot be finalized + transport-helper: check dup() return in get_exporter + compat/pread: check initial lseek for errors + last-modified: handle repo_parse_commit() failures + reftable tests: check reftable_table_init_ref_iterator() return + reftable/block: check deflateInit() return value + reftable: handle block-writer initialization errors + config: propagate launch_editor() failure in show_editor() + http: die on curl_easy_duphandle failure in get_active_slot A handful of code paths have been corrected to check return values from functions like curl_easy_duphandle(), deflateInit(), lseek(), dup(), and strbuf_getline_lf(), resolving several Coverity warnings about unchecked returns. Will merge to 'master'. cf. <an1k0d5fI4EVsfsM@xxxxxx> source: <pull.2179.v3.git.1786521801.gitgitgadget@xxxxxxxxx> * ds/trace2-tolerate-failed-timestamp (2026年07月15日) 1 commit - trace2: tolerate failed timestamp formatting The 'trace2' telemetry library has been updated to tolerate failures from system calls like gettimeofday() and datetime formatting functions, replacing potential program crashes with blank placeholder timestamps in the traces. Expecting a reroll. cf. <fbb118df-7c82-49a5-90bb-4458b7e9a850@xxxxxxxxx> source: <pull.2178.git.1784131932489.gitgitgadget@xxxxxxxxx> * cc/fast-import-usage (2026年08月11日) 12 commits (merged to 'next' on 2026年08月15日 at a0434930b4) + fast-import: remove useless from_stream argument + fast-import: use parse_options() for command line options + fast-import: use callbacks to parse some options + fast-import: use struct option for usage string + fast-import: move command state globals into 'struct fast_import_state' + fast-import: introduce 'struct fast_import_state' + fast-import: factor out option_*() functions + fast-import: use int for some bool flags + fast-import: localize 'i' into the 'for' loops using it + api-parse-options.adoc: document hidden and OPT_*_F option macros + api-parse-options.adoc: document per-option flags + parse-options: introduce OPT_HIDDEN_GROUP The usage string of 'git fast-import' has been updated to use the parse_options() API for displaying help, and its SYNOPSIS in the documentation has been standardized to match. Will merge to 'master'. cf. <CABPp-BE_gVtCF+Y0AAyXSXnJ2hUK0pJiWqEhkD8kVc4S8-y7kQ@xxxxxxxxxxxxxx> source: <20260811083314.2023489-1-christian.couder@xxxxxxxxx> * js/pack-objects-delta-size-t (2026年08月13日) 13 commits (merged to 'next' on 2026年08月17日 at b6778ce373) + packfile: widen `unpack_object_header_buffer()` to `size_t` + git-zlib: widen `git_deflate_bound()` to `size_t` + t/helper/test-pack-deltas: widen `do_compress()`'s maxsize local to `size_t` + http-push: widen `start_put()`'s size local from `ssize_t` to `size_t` + diff: widen `deflate_it()`'s bound local from int to `size_t` + archive-zip: widen `zlib_deflate_raw()`'s maxsize local to `size_t` + packfile, git-zlib: widen `use_pack()` and zstream avail fields to `size_t` + delta: widen `create_delta()` and `diff_delta()` to `size_t` + pack-objects: widen `mem_usage` and `try_delta()`'s out-param to `size_t` + pack-objects: widen `free_unpacked()` return to `size_t` + pack-objects: widen delta-cache accounting to `size_t` + delta: widen `create_delta_index()` parameter to `size_t` + diff-delta: widen `struct delta_index`' size fields to `size_t` The 'pack-objects' and delta-encoding code paths have been updated to use 'size_t' instead of 'unsigned long' for object sizes and offset limits, avoiding potential truncation issues on 64-bit Windows. Will merge to 'master'. cf. <xmqqbjb6t179.fsf@gitster.g> source: <pull.2175.v3.git.1786632952.gitgitgadget@xxxxxxxxx> * pz/fetch-submodule-errors-config (2026年07月16日) 2 commits - fetch: add fetch.submoduleErrors to make submodule fetch errors non-fatal - submodule: fix premature failure in recursive submodule fetch The 'git fetch' command can now configure how submodule fetch errors are handled via 'fetch.submoduleErrors' and '--submodule-errors', making them non-fatal. A premature failure during recursive submodule fetches has been fixed by deferring the error until the OID-based retry phase fails. Needs review. source: <20260716140956.1023740-1-paulius.zaleckas@xxxxxxxxx> * gr/add-e-use-apply-api (2026年07月10日) 1 commit - builtin/add.c: replace run_command() with direct apply_all_patches() call The application of the edited patch in 'git add -e' has been refactored to use the internal apply API directly, avoiding the need to spawn a 'git apply' subprocess. Needs review. source: <20260711061246.58079-1-gatlavishweshwarreddy26@xxxxxxxxx> * fz/rebase-autosquash-empty (2026年07月11日) 1 commit . sequencer: honor --empty when a fixup!/squash! empties its target A commit that is emptied by melding a 'fixup!' or 'squash!' commit during 'git rebase --autosquash' is now handled according to the '--empty' option, allowing it to be dropped, kept, or to halt the rebase. This topic has been ejected due to conflicts with 'pw/rebase-drop-notes-with-commit'. Expecting a reroll. cf. <DKJ2CZKJC6P0.VHLMCUDH6Z44@xxxxxxxxx> source: <20260711-fz-autosquash-empty-v3-1-d227b63eb511@xxxxxxxxx> * mm/lib-httpd-cgi-safe (2026年08月12日) 3 commits - t/lib-httpd: document writing concurrency-safe CGI helpers - t/lib-httpd: make http-429 first-request check atomic - t/lib-httpd: fix apply-one-time-script race under concurrent requests CGI helper scripts used by HTTP-related test scripts have been updated to use atomic filesystem operations, preventing race conditions when Apache handles concurrent requests. Needs review. source: <pull.2171.v3.git.1786583137.gitgitgadget@xxxxxxxxx> * ij/subtree-reject-v2-config (2026年07月06日) 2 commits - git-subtree: Bail out if we find output from Rust rewrite (test) - git-subtree: Bail out if we find output from Rust rewrite The shell script implementation of 'git subtree' has been updated to check for the presence of the configuration file of the new Rust implementation, preventing users from accidentally running the old script on repositories already managed by the new tool. Expecting a reroll. cf. <27219.20156.438730.881821@xxxxxxxxxxxxxxxxxxxxxx> source: <20260706115816.20267-1-ijackson@xxxxxxxxxxxxxxxxxxxxxx> * zy/apply-abandoned-header-fix (2026年07月01日) 1 commit - apply: avoid leaking abandoned git-header state A candidate 'git diff' header parsed by 'git apply' has been isolated in a temporary structure, preventing any partially parsed state from polluting the main patch structure and causing assertions to trip if the header is ultimately rejected. Needs review. source: <20260702041759.51572-1-zhihao.yao@xxxxxxxx> * ps/libgit-in-subdir (2026年07月12日) 3 commits . Move libgit.a sources into separate "lib/" directory . t/helper: prepare "test-example-tap.c" for introduction of "lib/" . Merge branch 'ps/odb-source-packed' into ps/libgit-in-subdir The source files for 'libgit.a' have been moved into a new 'lib/' directory to clean up the top-level directory and clearly separate library code. This topic has been ejected for now, as it causes too many evil merges with other topics. Waiting for response, stalled. cf. <xmqqqzkx9t95.fsf@gitster.g> cf. <al6yCTDjBRn2HGq0@com-79390> source: <20260713-pks-libgit-in-subdir-v4-0-696240876eb1@xxxxxx> * mm/line-log-limited-ops (2026年06月27日) 7 commits - diffcore-pickaxe: scope -G to the -L tracked range - diff: support --check with -L line ranges - line-log: support diff stat formats with -L - diff: extract a line-range diff helper for reuse - diff: emit -L hunk headers via xdiff's formatter - diff: simplify the line-range filter by classifying removals immediately - diff: rename and group the line-range filter for clarity (this branch is used by mm/diff-process-hunks.) The 'git log -L<range>:<path>' command has been taught to limit various 'diff' operations, such as '--stat', '--check', and '-G', to the specified range and path. Needs review. source: <pull.2152.v2.git.1782581342.gitgitgadget@xxxxxxxxx> * hn/history-squash (2026年08月20日) 8 commits - history: support editing squashed commit messages - history: create squashed commits without editing - history: protect branches when squashing a range - history: validate squash revision ranges - history: add skeleton for squash subcommand - sequencer: share the squash message marker helpers and flags - history: give commit_tree_ext a message template - history: extract helper for a commit's parent tree The experimental 'git history' command has been taught a new 'squash' subcommand to fold a range of commits into a single commit, with any descendants replayed on top. Waiting for response. cf. <xmqq4igov9h9.fsf@gitster.g> source: <pull.2337.v14.git.git.1787249432.gitgitgadget@xxxxxxxxx> * tb/midx-incremental-custom-base (2026年06月12日) 3 commits - midx-write: include packs above custom incremental base - midx: pass custom '--base' through incremental writes - t5334: expose shared `nth_line()` helper The 'git multi-pack-index write --incremental' command has been corrected to properly honor the '--base' option. Previously, the custom base was ignored by the normal write path; packs from layers above the selected base were incorrectly skipped by the pack exclusion logic, and reachability closure for bitmaps was broken. Expecting a reroll. cf. <an4uIQA09rDCwwBp@com-79390> source: <cover.1781294771.git.me@xxxxxxxxxxxx> * tc/replay-linearize (2026年07月28日) 3 commits - replay: offer an option to linearize the commit topology - replay: resolve the replay base outside pick_regular_commit() - replay: add helper to put entry into replayed_commits The 'git replay' command has been taught the '--linearize' option to drop merge commits and linearize the replayed history, mimicking 'git rebase --no-rebase-merges'. Waiting for response. cf. <anYLeQj4Sx2vZqvy@denethor> cf. <CABPp-BEFGku8msiJCcXburV+tcersr6uqEumKaPh-TguA1LjSg@xxxxxxxxxxxxxx> source: <20260728-toon-git-replay-drop-merges-v8-0-ced11dffe749@xxxxxxxxx> * mm/diff-process-hunks (2026年08月13日) 12 commits - fixup! diff: consult oid-only hunk providers via diff.<driver>.process - diff: consult oid-only hunk providers via diff.<driver>.process - userdiff: add diff.<driver>.process config - sub-process: add a gentle status read - sub-process: separate process lifecycle from hashmap management - blame: read precomputed hunks - diff: read precomputed hunks for stat output - diff: record precomputed hunks during stat output - diff-hunks: add the store format, library, and command - diff: introduce a hunk provider interface - gitattributes: document how external diff drivers relate to diff features - Merge branch 'mm/line-log-limited-ops' into mm/diff-process-hunks (this branch uses mm/line-log-limited-ops.) A new 'diff.<driver>.process' configuration has been introduced to allow a long-running external process to act as a hunk provider, enabling external tools to control which lines Git considers changed while leaving all output formatting (word diff, color, blame, etc.) to Git's standard pipeline. Waiting for response, stalled cf. <xmqqmrupr7yh.fsf@gitster.g> cf. <1f8fe709-ef19-496e-9857-8c2d24b29c56@xxxxxxxxx> source: <20260801174156.2998808-1-mmontalbo@xxxxxxxxx> * ec/commit-fixup-options (2026年05月26日) 2 commits - commit: allow -c/-C for all kinds of --fixup - commit: allow -m/-F for all kinds of --fixup Support for '-m', '-F', '-c', or '-C' options to supply a commit log message from outside the editor has been added for all 'git commit --fixup' variations. Needs review. source: <cover.1779792311.git.erik@xxxxxxxxxxx> * kk/merge-base-exhaustion (2026年08月11日) 11 commits (merged to 'next' on 2026年08月15日 at 3f836fa1e4) + commit-reach: remove commit-date ordering fallback + commit-reach: move min_generation check into paint_queue_get() + commit-reach: terminate merge-base walk when one paint side is exhausted + commit-reach: introduce struct paint_state with per-side counters + t6600: add clock-skew topologies and step counts for edge cases + commit-reach: add trace2 instrumentation to paint_down_to_common() + t6099: add side-exhaustion regression test + t6600: add test cases for side-exhaustion edge cases + test-lib-functions: improve diagnostic output for trace2 data assertions + Documentation/technical: add paint-down-to-common doc + Merge branch 'kk/commit-reach-find-all-fix' into kk/merge-base-exhaustion The merge-base computation has been optimized by stopping the walk early when one side's exclusive commits in the queue are exhausted, yielding significant speedups for queries with one-sided histories. Will merge to 'master'. cf. <CABPp-BHuh_8q6Hy2-Bk7H6Chdb4+eeW1f4LZU0szZ4zU9Eeo+w@xxxxxxxxxxxxxx> cf. <xmqqbjb7w1dq.fsf@gitster.g> source: <pull.2149.v8.git.1786440533.gitgitgadget@xxxxxxxxx>