What's cooking in git.git (Sep 2026, #08)
From: Junio C Hamano <hidden>
Date: 2026-09-22 00:11:58
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). Git 2.56-rc1 has been tagged. We may merge last-minute fixes before the final Git 2.56 release, but otherwise I do not expect any new feature topics to be ready before the final, so most of the in-flight topics will stay cooking in 'next' until then. As discussed at the Git Contributors' Summit, the version after the upcoming Git 2.56 will be Git 2.98, scheduled near the end of this year. 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/ -------------------------------------------------- [Graduated to 'master'] * tz/doc-pack-refs-and-refs-fixes (2026-09-15) 2 commits (merged to 'next' on 2026-09-16 at 127f3b13fa) + doc/refs: backtick-quote commands and options consistently + doc/pack-refs: convert synopsis and options to new style Doc updates. Graduated to 'master'. source: [ref] * yt/pathspec-negative-prefix (2026-09-14) 2 commits (merged to 'next' on 2026-09-16 at f4f244ea28) + dir: preserve pathspec prefix optimization with leading excludes + dir: do not apply prefix to negative pathspecs + Merge branch 'jc/pathspec-match-const' into yt/pathspec-negative-prefix The pathspec matching logic has been updated to avoid out-of-bounds memory accesses when a negative pathspec is shorter than the common prefix of positive pathspecs. Graduated to 'master'. source: [ref] -------------------------------------------------- [New Topics] * rr/upload-pack-swap-shallow-wanted-ref (2026-09-16) 1 commit - upload-pack: swap wanted-ref/shallow-info responses The server-side protocol v2 response order for 'wanted-refs' and 'shallow-info' has been swapped to match the client's expectation, fixing a fetch failure when the server has 'uploadpack.allowRefInWant' enabled and the client performs a shallow fetch. Will merge to 'next'. source: [ref] * bs/runtime-prefix-obsd-getexecpath (2026-09-16) 1 commit - exec_cmd: RUNTIME_PREFIX on OpenBSD systems Git on OpenBSD historically lacked an authoritative mechanism to resolve its executable path, as it doesn't support the KERN_PROC_PATHNAME sysctl. With OpenBSD 8.0 introducing getexecpath(3), it is now utilized to provide proper RUNTIME_PREFIX resolution instead of relying on argv[0] fallback. Waiting for response. cf. <xmqq4ifio83d.fsf@gitster.g> source: [ref] * js/coverity-fixes (2026-09-17) 7 commits - test-read-midx: check midx_fill_entry() result - oss-fuzz: handle reftable iterator initialization failures - t/unit-tests: check reftable iterator initialization - rerere: do not record failed conflict resolution data - midx: validate incremental MIDX pack IDs - gpg-interface: make signature-prefix matching length-aware - wrapper: guard writev_in_full() against signed overflow Assorted fixes for code paths that are not careful with boundary and error conditions. Will merge to 'next'? cf. <xmqq5x03u0xz.fsf@gitster.g> cf. <xmqq1parorz4.fsf@gitster.g> source: [ref] * yt/winansi-die-lasterr-fix (2026-09-20) 1 commit - compat/winansi: fix die_lasterr() argument formatting The error reporting machinery in the WinANSI compatibility layer has been simplified to pass the exact Windows error code and correctly format arguments for fatal errors. Waiting for response. cf. <xmqqwlsemsjt.fsf@gitster.g> source: [ref] * hd/diff-no-index-reverse-fix (2026-09-18) 1 commit - diff --no-index: fix -R with file/directory conflicts A bug in git diff --no-index that mishandled reverse (-R) output when conflicts existed between a file and a directory has been fixed. Will merge to 'next'? cf. [ref] cf. [ref] source: [ref] * js/gitlab-ci-windows-rust (2026-09-19) 4 commits - ci(gitlab,windows): provide GNU Rust's host-linker support - ci(gitlab,windows): fix Rust setup for GitLab's MinGW build - ci(gitlab,windows): preserve exclusions during dependency setup - ci(gitlab,windows): provision GNU Rust for SDK-based MinGW builds The Windows GitLab CI job has been updated to provision and use the GNU Rust toolchain for MinGW builds, fixing job failures caused by incomplete Rust setup and missing linker support. Will merge to 'next'? cf. [ref] source: [ref] -------------------------------------------------- [Cooking] * jc/advice-config-set-global (2026-09-14) 1 commit - advice: give cut-and-pasteable advice to squelch The advice subsystem has been updated to suggest using the '--global' option when recommending a command snippet to squelch future advice messages, since global configuration is generally more appropriate for user-level preferences than per-repository settings. Needs review. source: <xmqq33vb4hma.fsf@gitster.g> * sg/precompile-git-compat-util (2026-09-14) 4 commits (merged to 'next' on 2026-09-21 at 68acceee5b) + Makefile: precompile "git-compat-util.h" + Makefile: reintroduce REFTABLE_OBJS + cmake: remove any "$(*_OBJS)" variables when parsing Makefile for sources + Makefile: remove XDIFF_OBJS initialization The 'Makefile' has been taught to precompile 'git-compat-util.h' to speed up overall compilation, while excluding sources that do not include the compatibility header. Will cook in 'next'. source: [ref] * of/commit-reach-repo-awareness (2026-09-16) 1 commit - commit-reach: parse commits in the given repository The can_all_from_reach() and can_all_from_reach_with_flag() functions have been updated to accept a repository context, preventing bugs where submodule merging incorrectly reads from the superproject's commit-graph. Will merge to 'next'. source: [ref] * hn/range-diff-matched-only (2026-09-15) 1 commit - range-diff: add --matched-only to skip one-sided commits The 'git range-diff' command has been augmented with a '--matched-only' option to skip commits that are only present on one side, allowing users to easily focus on only the commits that have been retained. Needs review. source: [ref] * jc/cocci-free-updates (2026-09-11) 2 commits (merged to 'next' on 2026-09-16 at 35b8bafa06) + cocci: FREE_AND_NULL(E) is safe to call on NULL + cocci: remove risky "if (!E) free(E)" conversion Updates to Coccinelle semantic patches to correctly handle the 'FREE_AND_NULL()' macro and avoid generating broken transformations for negated pointer checks. Will cook in 'next'. cf. [ref] source: <xmqqld978mok.fsf@gitster.g> source: <xmqqh5jv8m4w.fsf@gitster.g> * jt/object-file-batch-fsync-fix (2026-09-13) 2 commits - object-file: flush transaction packfile before migrating objects - object-file: lift ODB reprepare out of packfile flush When 'core.fsyncMethod' is set to 'batch', the ODB transaction failed to properly flush large blob packfiles residing in the temporary directory before migrating the directory's contents to the main object store. The execution sequence has been corrected by performing the packfile flush before the temporary directory migration, averting failure. Waiting for review. cf. [ref] cf. <aqkGPcJdw3QagN0B@jtobler--20250820-SHC54> source: [ref] * ak/refs-files-root-ref-lock (2026-09-11) 1 commit (merged to 'next' on 2026-09-16 at c8568ea3e1) + refs/files: avoid packed-refs lock for root ref deletion The files backend has been updated to avoid unconditionally locking the 'packed-refs' file when deleting a root ref (which are never packed). Will cook in 'next'. cf. [ref] source: [ref] * tb/rerere-wait-for-merge-rr-lock (2026-09-14) 2 commits - rerere: go on at a conflict when the lock stays busy - rerere: wait for MERGE_RR.lock, and let the gc skip it Instead of failing to record conflicts to be resolved immediately, wait while "rerere gc" is ongoing. Needs review. source: [ref] * pp/midx-write-skip-empty (2026-09-08) 1 commit - midx-write: skip writes with no object entries The `git multi-pack-index write` command has been updated to silently return success when there are no object entries to index. This avoids writing empty `multi-pack-index` layers, which previously caused subsequent incremental midx writes using the `--bitmap` option to fail when attempting to load the missing reverse index. Waiting for review. cf. <aqAkfGZtLJ97nG1m@com-79390> cf. [ref] source: [ref] * jk/merge-ll-tempfile-cleanup (2026-09-11) 3 commits - merge-ll: use tempfile API for external driver files - merge-ll: catch close() errors when writing external tempfiles - merge-ll: use strbuf to read back external merge result The external merge driver in 'git merge' now uses the tempfile API to create its temporary files. This ensures that these temporaries are reliably cleaned up even when the merge driver or its parent Git process is terminated abruptly. Expecting a reroll. cf. [ref] source: [ref] * mh/rust-crate-subdir (2026-09-16) 1 commit - move rust gitcore crate to a different subdirectory The Rust code and its 'Cargo.toml' file have been moved from the top-level repository root and 'src/' directory into a dedicated 'rust/' subdirectory. This avoids confusing Cargo's packaging mechanism when the Git repository is included as a submodule in other Rust projects. Waiting for review. cf. <yc4bgjoyxnm6o7q4gwols4d6zvdrq3ydw2c65wjdwof3hjyde6@2osv37jtuxx3> source: [ref] * ps/ref-storage-format (2026-09-09) 13 commits (merged to 'next' on 2026-09-16 at 8937a6240b) + setup: allow "--ref-storage-format=" to specify a payload + setup: rename "init.defaultRefFormat" to "init.defaultRefStorageFormat" + t: rename GIT_TEST_DEFAULT_REF_FORMAT + setup: rename ref storage format environment variables + setup: refactor how we configure the ref storage format + refs: expose function to parse reference URIs + help: rename "default-ref-format" to "default-ref-storage-format" + builtin/rev-parse: rename "--show-ref-format" to "--show-ref-storage-format" + builtin/submodule: rename "--ref-format=" to "--ref-storage-format=" + builtin/refs: rename "--ref-format=" to "--ref-storage-format=" + builtin/clone: rename "--ref-format=" to "--ref-storage-format=" + builtin/init: rename "--ref-format=" to "--ref-storage-format=" + parse-options: allow for hidden aliases The terminology regarding reference storage formats has been unified across command-line options, environment variables, configuration variables, and source code, standardizing on the phrase "ref storage format" (e.g., `--ref-storage-format`, `'GIT_REF_STORAGE_FORMAT'`). Additionally, the `--ref-storage-format` option has been updated to accept payloads in the form `<format>://<payload>`. Will cook in 'next'. cf. [ref] cf. [ref] source: [ref] * ta/command-list-guides-sync-lint (2026-09-10) 2 commits - lint-docs: check the guide list in command-list.txt - command-list.txt: add gitformat-loose(5) and gitpacking(7) - Merge branch 'kh/doc-datamodel' into ta/command-list-guides-sync-lint A new linter test has been added to Documentation/lint-manpages.sh to ensure that all non-command manual pages (guides and developer interfaces) listed in Documentation/Makefile are present in command-list.txt, replacing an older comment that reminded developers to keep them in sync. Needs review. cf. <xmqq1pb2s33e.fsf@gitster.g> source: [ref] * ap/var-broken-down-idents (2026-09-14) 1 commit - var: support broken-down idents, signing key, multiple args, and -z The 'git var' command has been extended to expose individual identity components ('GIT_AUTHOR_NAME', etc.) and the commit signing key, and can now accept multiple variables to query at once, safely formatting the output with a new '-z' option. Expecting a reroll. cf. [ref] source: [ref] * tc/push-force-if-includes-fixes (2026-09-17) 3 commits - push: --force-if-includes should allow fast-forward - push: fix --force-if-includes non-branch advice - push: check pushed ref for --force-if-includes The '--force-if-includes' protection for 'git push' has been updated to consult the reflog of the local branch being pushed, rather than incorrectly checking the reflog of a local branch that shares the name of the remote destination branch. The push advice for detached HEAD scenarios has also been adjusted to indicate that the remote ref cannot be verified locally. A regression that caused perfectly valid fast-forward pushes to be rejected when reflogs were expired has been fixed. Needs review. source: [ref] * as/push-force-if-includes-no-reflog (2026-09-05) 1 commit - push: fix --force-if-includes when remote-tracking ref has no reflog The timestamp used for checking the reflog of a remote-tracking branch during 'git push --force-if-includes' was left uninitialized when the reflog was completely empty, which has been corrected. Waiting for review. cf. <xmqqjyowz9oq.fsf@gitster.g> cf. [ref] source: [ref] * tb/rerere-lock-grace (2026-09-17) 3 commits - sequencer: disable auto maintenance in spawned commands - rebase, cherry-pick, revert: run auto maintenance when done - config: add git_config_append_parameter() The sequencer machinery (used by 'git rebase', 'git cherry-pick', and 'git revert') has been updated to defer automatic maintenance tasks until the end of the operation, preventing nested 'git commit', 'git merge', and 'exec' commands from triggering GC operations that could contend for locks or delete open packs while the sequence is in progress. Needs review. source: [ref] * cc/lazy-fetch-trusted-bit (2026-09-08) 5 commits - builtin/upload-pack: set GIT_NO_LAZY_FETCH to 0 on trusted repo - promisor-remote: prevent infinite recursion when lazy fetching - upload-pack: read uploadpack.lazyFetchTrusted - 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. <xmqq7bkvy74h.fsf@gitster.g> cf. <xmqqqzj3wr24.fsf@gitster.g> cf. <xmqqmrtrwq0k.fsf@gitster.g> source: [ref] * cc/early-scan-options (2026-09-02) 6 commits - fast-import: use early_scan_options() for --allow-unsafe-features - parse-options: build early scan options from a struct option array - parse-options: add parse_options_takes_argument() - rev-parse: fix "--" detection when it is an option value - bisect: fix "--" detection when a term name is "--" - parse-options: add early_scan_options() The process of parsing command-line options in commands that perform an early scan over their arguments (such as 'git bisect', 'git rev-parse', and 'git fast-import') has been unified using a new early-scan sub-API, which parses and skips known options taking separate values to prevent logic bugs. Waiting for response. cf. <xmqqpkyviizc.fsf@gitster.g> source: [ref] * 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. Expecting a reroll. cf. [ref] source: [ref] * jc/checkout-refactor (2026-08-30) 8 commits - checkout: move post_checkout_hook() to checkout.c - checkout: wrap overly long lines - checkout: restructure switch, restore, and checkout entrypoints - checkout: extract branch setup and tracking helpers - checkout: extract option validation and pathspec helpers - checkout: validate stage and merge option compatibility in checkout_paths() - checkout: validate new branch name in checkout_branch() - checkout: pass cb_option explicitly to branch name parsers The front-end code for 'git checkout', 'git switch', and 'git restore' has been restructured to cleanly separate their pathspec and branch handling, eliminating a common bottleneck and paving the way to libify utility helpers. Waiting for response. cf. <xmqqo6el1xz0.fsf@gitster.g> cf. <xmqqse3x1y20.fsf@gitster.g> source: [ref] * ll/doc-pushcert-if-asked (2026-08-29) 1 commit - doc: remote-helpers: option pushcert if-asked The remote helper documentation for the 'pushcert' option has been updated to mention that it can also take 'if-asked', reflecting the existing implementation in the code. Needs review. source: [ref] * ws/squelch-svn-migrate (2026-08-27) 2 commits - Makefile: add NO_GIT_SVN knob to skip building/installing git-svn - git-svn: don't print v1-layout migration noise when there's nothing to migrate Needs review. source: [ref] * dw/config-read-both-global (2026-08-23) 3 commits - config: read global scope via config_sequence - config: let sequence require a successful file - path: use forward slashes in XDG config on Windows The git config --global read operations have been updated to respect both $HOME/.gitconfig and $XDG_CONFIG_HOME/git/config, fixing an inconsistency where only the former was read when both configuration files are present. Expecting a reroll. cf. [ref] source: [ref] * vv/branch-recurse-no-start-ref (2026-08-21) 2 commits - branch: allow recursion with no tracking name - branch: do not track a start point with no ref The --recurse-submodules option in 'git branch' has been fixed to avoid a crash when the start point is not a reference (e.g., a raw object ID). The creation path now skips setting up tracking and properly forwards the absent tracking name to the submodule helper. Needs review. source: [ref] * ps/odb-alternates-at-creation (2026-09-10) 9 commits (merged to 'next' on 2026-09-15 at 4acaa6a8aa) + odb/source: remove the ability to write alternates + builtin/clone: write alternates via `odb_create_on_disk()` + odb/source: support writing alternates when creating the database + builtin/clone: move setup of alternates for non-shared local clones + builtin/clone: move setup of alternates for shared local clones + builtin/clone: refactor handling of "--reference{,-if-able}" + builtin/clone: move around `setup_reference()` + builtin/clone: defer setup of the object database + setup: split up concerns of `init_db()` + Merge branch 'ps/odb-eagerly-load-alternates' into ps/odb-alternates-at-creation The setup of alternates has been deferred to object database creation time during clone, which drops the unused ad-hoc alternate writing API, simplifying the object database backend interface. Will cook in 'next'. cf. [ref] source: [ref] * as/utimensat-utimes (2026-08-21) 3 commits - compat/posix: drop legacy <utime.h> header and shims - treewide: use utimensat(2) instead of legacy utime(3p) - compat/posix: introduce utimensat(2) wrapper The codebase has been updated to use the newer utimensat() POSIX function instead of the obsolescent utime(), allowing high-precision timestamps while preserving fallback compatibility. Waiting for response for too long, stalled cf. [ref] source: [ref] * kn/receive-report-hook (2026-09-14) 5 commits (merged to 'next' on 2026-09-15 at aa6cbdb87e) + receive-pack: coccinelle fix + hook: introduce the receive-report hook + receive-pack: move message generation to separate function + receive-pack: drop static variables to track report status version + doc: add proc-receive hook info in 'git-receive-pack.adoc' 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. Will cook in 'next'. source: [ref] source: <xmqqwlsn31gq.fsf_-_@gitster.g> * 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: [ref] * 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: [ref] * gg/http-ssl-verify-status (2026-09-15) 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. Will merge to 'next'? cf. <xmqqv785uha7.fsf@gitster.g> source: [ref] * 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. Waiting for response for too long, stalled cf. [ref] source: [ref] * dk/use-nsec-runtime (2026-09-11) 3 commits (merged to 'next' on 2026-09-15 at 67ef6d82ef) + 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. Will cook in 'next'. cf. [ref] source: [ref] * bc/restrict-hex-to-lowercase (2026-09-07) 7 commits - hex: allow only lowercase object IDs in breaking changes mode - t5324: adjust tests for corrupt commit-graph - 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. Needs review. source: [ref] * kj/repo-info-more-path-keys (2026-09-11) 7 commits - repo: add path.cdup - 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. <xmqqse3fbudk.fsf@gitster.g> cf. <xmqqcxujbser.fsf@gitster.g> source: [ref] * tc/last-modified-bloom (2026-09-01) 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. [ref] cf. [ref] source: [ref] * ds/trace2-tolerate-failed-timestamp (2026-08-31) 7 commits - trace2: remove use of xcalloc() - trace2: remove use of ALLOC_GROW() - trace2: remove use of xstrfmt() - trace2: remove use of ALLOC_ARRAY() - trace2: remove use of xstrdup() - trace2: tolerate failed timestamp formatting - banned-die: create header for banning of functions Functions like `xstrfmt()` and `xcalloc()` have been banned from use in the trace2 API codebase to prevent calls to `die()` which lead to unwanted process exits and recursion when memory allocation fails. Needs review. source: [ref] * 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: [ref] * fz/rebase-autosquash-empty (2026-08-27) 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. Waiting for response. cf. [ref] source: [ref] * 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. [ref] source: [ref] * mm/line-log-limited-ops (2026-09-02) 7 commits - diffcore-pickaxe: limit -G to the -L tracked range - diff: support --check with -L line ranges - diff: support 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 line-range filter struct and clarify fields (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: [ref] * hn/history-squash (2026-09-08) 8 commits (merged to 'next' on 2026-09-15 at 28dd773b8b) + 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. Will cook in 'next'. cf. <xmqqik4fv4v1.fsf@gitster.g> source: [ref] * 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> cf. [ref] source: [ref] * mm/diff-process-hunks (2026-08-13) 11 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. Expecting a reroll. cf. [ref] source: [ref] * kh/format-patch-range-diff-notes (2026-08-24) 3 commits . format-patch: learn --[no-]range-diff-notes . revision.h: rename struct member to reflect notes role . format-patch: simplify get_notes_arg parameters The 'format-patch' command has been updated with options to configure notes specifically for range-diff output, allowing them to differ from the notes displayed on the patches themselves. Expecting a reroll. cf. [ref] source: [ref]