What's cooking in git.git (Feb 2026, #05)
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 are candidate to be in a future release). Commits prefixed with '-' are only in 'seen', and aren't considered "accepted" at all and may be annotated with an URL to a message that raises issues but they are no means exhaustive. A topic without enough support may be discarded after a long period of no activity (of course they can be resubmit when new interests arise).
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.
We will be rewinding the tip of 'next' soonish.
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']
* am/doc-github-contributiong-link-to-submittingpatches (2026-01-31) 1 commit (merged to 'next' on 2026-02-04 at 1f4534468b)
+ .github/CONTRIBUTING.md: link to SubmittingPatches on git-scm.com
GitHub repository banner update.
source: <[email protected]>
* cf/c23-const-preserving-strchr-updates-0 (2026-02-05) 2 commits (merged to 'next' on 2026-02-06 at ac9d269e5c)
+ gpg-interface: remove an unnecessary NULL initialization
+ global: constify some pointers that are not written to
ISO C23 redefines strchr and friends that tradiotionally took
a const pointer and returned a non-const pointer derived from it to preserve constness (i.e., if you ask for a substring in a const
string, you get a const pointer to the substring). Update code
paths that used non-const pointer to receive their results that did
not have to be non-const to adjust.
source: <342b01acd42f1fcaa3abefa38dc589e12ccb1134.1770261829.git.collin.funk1@gmail.com>
* cs/subtree-reftable-testfix (2026-02-03) 1 commit (merged to 'next' on 2026-02-05 at d953fc69cc)
+ contrib/subtree: fix tests with reftable backend
Test fix (in contrib/)
source: <[email protected]>
* hs/t9160-test-paths (2026-02-02) 1 commit
(merged to 'next' on 2026-02-04 at 0d4010771a)
+ t9160:modernize test path checking
Test update.
source: <[email protected]>
* jc/ci-test-contrib-too (2026-02-06) 2 commits
(merged to 'next' on 2026-02-06 at 2890869b63)
+ ci: ubuntu: use GNU coreutils for dirname
+ test: optionally test contrib in CI
Test contrib/ things in CI to catch breakages before they enter the "next" branch.
source: <[email protected]>
source: <[email protected]>
* jc/diff-highlight-main-master-testfix (2026-02-03) 1 commit (merged to 'next' on 2026-02-05 at 128a77dfe5)
+ diff-highlight: allow testing with Git 3.0 breaking changes
Test fix (in contrib/)
source: <[email protected]>
* jt/odb-transaction-per-source (2026-02-02) 4 commits (merged to 'next' on 2026-02-06 at 9f85ed3c47)
+ odb: transparently handle common transaction behavior
+ odb: prepare struct odb_transaction to become generic
+ object-file: rename transaction functions
+ odb: store ODB source in struct odb_transaction
Transaction to create objects (or not) is currently tied to the repository, but in the future a repository can have multiple object sources, which may have different transaction mechanisms. Make the odb transaction API per object source.
source: <[email protected]>
* kh/doc-shortlog-fix (2026-02-03) 1 commit
(merged to 'next' on 2026-02-04 at 0b24d64c43)
+ doc: shortlog: put back trailer paragraphs
Doc fix.
source: <[email protected]>
* mc/doc-send-email-signed-off-by-cc (2026-02-05) 1 commit (merged to 'next' on 2026-02-06 at 2a3d683680)
+ doc: send-email: correct --no-signed-off-by-cc misspelling
Docfix.
source: <[email protected]>
* ps/commit-list-functions-renamed (2026-01-15) 3 commits (merged to 'next' on 2026-02-06 at f7ef001af4)
+ commit: rename free_commit_list() to conform to coding guidelines
+ commit: rename reverse_commit_list() to conform to coding guidelines
+ commit: rename copy_commit_list() to conform to coding guidelines
Rename three functions around the commit_list data structure.
source: <20260115-pks-commit-list-coding-guidelines-v1-0-c58868dbf412@pks.im>
* rs/blame-ignore-colors-fix (2026-02-01) 1 commit (merged to 'next' on 2026-02-04 at 305ecc6b61)
+ blame: fix coloring for repeated suspects
"git blame --ignore-revs=... --color-lines" did not account for ignored revisions passing blame to the same commit an adjacent line gets blamed for.
source: <[email protected]>
* sb/merge-ours-sparse (2026-02-06) 2 commits
(merged to 'next' on 2026-02-06 at 64333814d3)
+ merge-ours: integrate with sparse-index
+ merge-ours: drop USE_THE_REPOSITORY_VARIABLE
"git merge-ours" is taught to work better in a sparse checkout.
source: <[email protected]>
* sd/doc-my1c-api-config-reference-fix (2026-02-05) 1 commit (merged to 'next' on 2026-02-06 at 222e701dd5)
+ doc: fix repo_config documentation reference
Docfix.
source: <[email protected]>
* sp/show-index-warn-fallback (2026-01-30) 2 commits (merged to 'next' on 2026-02-04 at 58399695e4)
+ show-index: use gettext wrapping in user facing error messages
+ show-index: warn when falling back to SHA-1 outside a repository
When "git show-index" is run outside a repository, it silently defaults to SHA-1; the tool now warns when this happens.
source: <[email protected]>
* tc/last-modified-not-a-tree (2026-01-30) 4 commits
(merged to 'next' on 2026-02-06 at b3dcd27ef8)
+ last-modified: verify revision argument is a commit-ish
+ last-modified: remove double error message
+ last-modified: fix memory leak when more than one commit is given
+ last-modified: rewrite error message when more than one commit given
Giving "git last-modified" a tree (not a commit-ish) died an uncontrolled death, which has been corrected.
cf. <[email protected]>
source: <[email protected]>
* tc/memzero-array (2026-02-03) 1 commit
(merged to 'next' on 2026-02-05 at 0755d57f09)
+ cocci: extend MEMZERO_ARRAY() rules
Coccinelle rules update.
source: <[email protected]>
--------------------------------------------------
[New Topics]
* ps/pack-concat-wo-backfill (2026-02-11) 1 commit
- builtin/pack-objects: don't fetch objects when merging packs
"git pack-objects --stdin-packs" with "--exclude-promisor-objects" fetched objects that are promised, which was not wanted. This has been fixed.
Will merge to 'next'?
source: <20260211-pks-pack-objects-stdin-skip-backfill-fetch-v1-1-870cad56d8ae@pks.im>
* jc/doc-cg-c-comment (2026-02-11) 1 commit
(merged to 'next' on 2026-02-12 at d1286b26eb)
+ CodingGuidelines: document // comments
A CodingGuidelines update.
Will merge to 'master'.
source: <[email protected]>
* jc/doc-cg-needswork (2026-02-12) 1 commit
- CodingGuidelines: document NEEDSWORK comments
A CodingGuidelines update.
Will merge to 'next'?
source: <[email protected]>
* jh/alias-i18n (2026-02-11) 3 commits
- alias: support non-alphanumeric names via subsection syntax
- alias: prepare for subsection aliases
- help: use list_aliases() for alias listing
Extend the alias configuration syntax to allow aliases using characters outside ASCII alphanumeric (plus '-').
Will merge to 'next'?
source: <[email protected]>
* ak/t9812-test-path-is-helpers (2026-02-11) 1 commit (merged to 'next' on 2026-02-13 at a9746d98e4)
+ t9812: modernize test path helpers
Test update.
Will merge to 'master'.
source: <[email protected]>
* hy/diff-lazy-fetch-with-break-fix (2026-02-12) 2 commits
- SQUASH???
- diffcore-break: prevent dangling pointer
A prefetch call can be triggered to access a stale diff_queue entry after diffcore-break breaks a filepair into two and freed the original entry that is no longer used, leading to a segfault, which has been corrected.
Expecting a reroll?
source: <[email protected]>
* ps/history-ergonomics-updates (2026-02-13) 5 commits
- Documentation/git-history: document default for "--update-refs="
- builtin/history: rename "--ref-action=" to "--update-refs="
- builtin/history: replace "--ref-action=print" with "--dry-run"
- builtin/history: check for merges before asking for user input
- builtin/history: perform revwalk checks before asking for user input
UI improvements for "git history reword".
Will merge to 'next'?
source: <[email protected]>
* pw/diff-anchored-optim (2026-02-12) 1 commit (merged to 'next' on 2026-02-13 at a8e8191f03)
+ diff --anchored: avoid checking unmatched lines
"git diff --anchored=<text>" has been optimized.
Will merge to 'master'.
source: <2a8cc2d6c37f25a58823b501500165d597321749.1770911599.git.phillip.wood@dunelm.org.uk>
* ac/string-list-sort-u-and-tests (2026-02-12) 1 commit . sparse-checkout: use string_list_sort_u
source: <[email protected]>
--------------------------------------------------
[Cooking]
* dk/complete-stash-import-export (2026-02-07) 1 commit
- completion: add stash import, export
Command line completion (in contrib/) update.
Comments?
source: <[email protected]>
* kh/doc-am-format-sendmail (2026-02-12) 1 commit (merged to 'next' on 2026-02-13 at 8850dc2fa9)
+ doc: add caveat about round-tripping format-patch
Doc update.
Will merge to 'master'.
source: <[email protected]>
* kh/doc-patch-id-4 (2026-02-07) 3 commits
- doc: patch-id: see also git-cherry(1)
- doc: patch-id: add script example
- doc: patch-id: emphasize multi-patch processing
Doc update.
Comments?
source: <[email protected]>
* pw/commit-msg-sample-hook (2026-02-13) 2 commits
- templates: detect commit messages containing diffs
- templates: add .gitattributes entry for sample hooks
Update sample commit-msg hook to complain when a log message has material mailinfo considers the end of log message in the middle.
Will merge to 'next'.
source: <[email protected]>
* bk/t2003-modernise (2026-02-09) 1 commit
(merged to 'next' on 2026-02-10 at 561a73205e)
+ t2003: modernize path existence checks using test helpers
Test update.
Will merge to 'master'.
source: <[email protected]>
* kh/doc-am-xref (2026-02-09) 4 commits
- doc: am: fill out hook discussion
- doc: am: add missing config am.messageId
- doc: am: say that --message-id adds a trailer
- doc: am: normalize git(1) command links
Doc update.
Comments?
source: <[email protected]>
* kh/doc-rerere-options-xref (2026-02-10) 1 commit (merged to 'next' on 2026-02-10 at 1ade94535a)
+ doc: rerere-options.adoc: link to git-rerere(1)
Doc update.
Will merge to 'master'.
source: <[email protected]>
* ps/ci-gitlab-msvc-updates (2026-02-11) 7 commits
- gitlab-ci: handle failed tests on MSVC+Meson job
- gitlab-ci: use "run-test-slice-meson.sh"
- ci: make test slicing consistent across Meson/Make
- github: fix Meson tests not executing at all
- meson: fix MERGE_TOOL_DIR with "--no-bin-wrappers"
- ci: don't skip smallest test slice in GitLab
- ci: handle failures of test-slice helper
CI update.
Will merge to 'next'?
source: <[email protected]>
* ps/tests-wo-iconv-fixes (2026-02-09) 4 commits
- t6006: don't use iconv(1) without ICONV prereq
- t5550: add ICONV prereq to tests that use "$HTTPD_URL/error"
- t4205: improve handling of ICONV prerequisite
- t4xxx: don't use iconv(1) without ICONV prereq
Some tests assumed "iconv" is available without honoring ICONV prerequisite, which has been corrected.
Comments?
source: <[email protected]>
* pw/meson-doc-mergetool (2026-02-09) 1 commit
- meson: fix building mergetool docs
Update build precedure for mergetool documentation in meson-based builds.
WIll merge to 'next'.
source: <604c79018992dee019205741934508091cdd1e47.1770631599.git.phillip.wood@dunelm.org.uk>
* rs/clean-includes (2026-02-08) 1 commit
(merged to 'next' on 2026-02-10 at 883d07f2eb)
+ remove duplicate includes
Clean up redundant includes of header files.
Will merge to 'master'.
source: <[email protected]>
* rs/commit-commit-stack (2026-02-08) 1 commit
(merged to 'next' on 2026-02-10 at c1a50b2859)
+ commit: use commit_stack
Code clean-up to use the commit_stack API.
Will merge to 'master'.
source: <[email protected]>
* rs/version-wo-the-repository (2026-02-08) 1 commit (merged to 'next' on 2026-02-10 at 80809d2b3d)
+ version: stop using the_repository
Code clean-up.
Will merge to 'master'.
source: <[email protected]>
* rs/xdiff-wo-the-repository (2026-02-09) 1 commit (merged to 'next' on 2026-02-10 at dbb8a23008)
+ xdiff-interface: stop using the_repository
Reduce dependency on the_repository of xdiff-interface layer.
Will merge to 'master'.
source: <[email protected]>
* sd/t7003-test-path-is-helpers (2026-02-09) 1 commit (merged to 'next' on 2026-02-10 at 5e3bc9f2b9)
+ t7003: modernize path existence checks using test helpers
Test updates.
Will merge to 'master'.
source: <[email protected]>
* ds/config-list-with-type (2026-02-09) 5 commits
- config: make 'git config list --type=<X>' work
- config: create special init for list mode
- config: allow format_config() to filter
- parse: add git_parse_maybe_pathname()
- config: move show_all_config()
"git config list" is taught to show the values interpreted for specific type with "--type=<X>" option.
Comments?
source: <[email protected]>
* jc/doc-rerere-update (2026-02-09) 1 commit
(merged to 'next' on 2026-02-10 at 88a6c151d7)
+ rerere: minor documantation update
Doc update.
Will merge to 'master'.
source: <[email protected]>
* rr/gitweb-mobile (2026-02-09) 5 commits
- gitweb: let page header grow on mobile for long wrapped project names
- gitweb: fix mobile footer overflow by wrapping text and clearing floats
- gitweb: fix mobile page overflow across log/commit/blob/diff views
- gitweb: prevent project search bar from overflowing on mobile
- gitweb: add viewport meta tag for mobile devices
"gitweb" has been taught to be mobile friendly.
Comments?
source: <[email protected]>
* kn/osxkeychain-buildfix (2026-02-10) 1 commit
- osxkeychain: define build targets in the top-level Makefile.
Simplify build procedure for oxskeychain (in contrib/).
Will merge to 'next'?
source: <[email protected]>
* yt/merge-file-outside-a-repository (2026-02-07) 1 commit (merged to 'next' on 2026-02-10 at ee1ced4120)
+ merge-file: honor merge.conflictStyle outside of a repository
"git merge-file" can be run outside a repository, but it ignored all configuration, even the per-user ones. The command now uses available configuration files to find its customization.
Will merge to 'master'.
source: <[email protected]>
* aa/add-p-no-auto-advance (2026-02-13) 4 commits
- add-patch: allow interfile navigation when selecting hunks
- add-patch: allow all-or-none application of patches
- add-patch: modify patch_update_file() signature
- interactive -p: add new --auto-advance flag
"git add -p" learned a new mode that allows the user to revisit a file that was already dealt with.
Comments?
source: <[email protected]>
* kn/ref-location (2026-02-09) 4 commits
- refs: add GIT_REFERENCE_BACKEND to specify reference backend
- refs: allow reference location in refstorage config
- refs: forward and use the reference storage payload
- refs: extract out refs_create_refdir_stubs()
Allow the directory in which reference backends store their data to be specified.
Expecting a reroll or two?
cf. <[email protected]>
source: <[email protected]>
* ar/config-hooks (2026-02-04) 5 commits
- hook: allow out-of-repo 'git hook' invocations
- hook: include hooks from the config
- hook: introduce "git hook list"
- hook: run a list of hooks
- Merge branch 'ar/run-command-hook-take-2' into ar/config-hooks (this branch is used by ar/parallel-hooks; uses ar/run-command-hook-take-2.)
Needs review.
source: <[email protected]>
* jc/whitespace-incomplete-line (2026-02-04) 1 commit
- whitespace: symbolic links usually lack LF at the end
It does not make much sense to apply the "incomplete-line" whitespace rule to symbolic links, whose contents almost always lack the final newline. "git apply" and "git diff" are now taught to exclude them for a change to symbolic links.
Will merge to 'next'?
source: <[email protected]>
* ps/meson-gitk-git-gui (2026-02-04) 1 commit
- meson: wire up gitk and git-gui
Plumb gitk/git-gui build and install procedure in meson based builds.
Expecting a pull request for gitk.
source: <[email protected]>
* uk/signature-is-good-after-key-expires (2026-02-04) 1 commit
- gpg-interface: signatures by expired keys are fine
A signature on a commit that was GPG signed long time ago ought to be still valid after the key that was used to sign it has expired, but we showed them in alarming red.
Will merge to 'next'?
source: <[email protected]>
* ar/parallel-hooks (2026-02-04) 5 commits
- hook: allow runtime enabling extensions.hookStdoutToStderr
- hook: introduce extensions.hookStdoutToStderr
- hook: allow parallel hook execution
- config: add a repo_config_get_uint() helper
- Merge branch 'ar/config-hooks' into ar/parallel-hooks (this branch uses ar/config-hooks and ar/run-command-hook-take-2.)
Needs review.
source: <[email protected]>
* mc/tr2-process-ancestry-cleanup (2026-02-13) 6 commits
- t0213: add trace2 cmd_ancestry tests
- test-tool: extend trace2 helper with 400ancestry
- trace2: emit cmd_ancestry data for Windows
- trace2: refactor Windows process ancestry trace2 event
- build: include procinfo.c impl for macOS
- trace2: add macOS process ancestry tracing
Add process ancestry data to trace2 on macOS to match what we already do on Linux and Windows. Also adjust the way Windows implementation reports this information to match the other two.
Will merge to 'next'.
source: <[email protected]>
* jc/checkout-switch-restore (2026-01-29) 2 commits
- checkout: tell "parse_remote_branch" which command is calling it
- checkout: pass program-readable token to unified "main"
"git switch <name>", in an attempt to create a local branch <name> after a remote tracking branch of the same name gave an advise message to disambiguate using "git checkout", which has been updated to use "git switch".
Will merge to 'next'?
source: <[email protected]>
* ps/for-each-ref-in-fixes (2026-02-05) 4 commits
- bisect: simplify string_list memory handling
- bisect: fix misuse of refs_for_each_ref_in()
- pack-bitmap: fix bug with exact ref match in "pack.preferBitmapTips"
- pack-bitmap: deduplicate logic to iterate over preferred bitmap tips
A handful of places used refs_for_each_ref_in() API incorrectly, which has been corrected.
Will merge to 'next'?
cf. <[email protected]>
source: <20260206-b4-pks-fix-for-each-ref-in-misuse-v3-0-1e050c3d6a50@pks.im>
* ja/doc-synopsis-style-even-more (2026-02-05) 4 commits (merged to 'next' on 2026-02-09 at d732b9d6a0)
+ doc: convert git-show to synopsis style
+ doc: fix some style issues in git-clone and for-each-ref-options
+ doc: finalize git-clone documentation conversion to synopsis style
+ doc: convert git-submodule to synopsis style
A handful of documentation pages have been modernized to use the "synopsis" style.
Will merge to 'master'.
source: <[email protected]>
* ps/object-info-bits-cleanup (2026-02-11) 5 commits
- odb: convert odb_has_object() flags into an enum
- odb: convert object info flags into an enum
- odb: drop gaps in object info flag values
- builtin/fsck: fix flags passed to odb_has_object()
- builtin/backfill: fix flags passed to odb_has_object()
A couple of bugs in use of flag bits around odb API has been corrected, and the flag bits reordered.
Will merge to 'next'?
source: <[email protected]>
* pw/xdiff-cleanups (2026-01-26) 2 commits
(merged to 'next' on 2026-02-11 at e6df42d605)
+ xdiff: remove unused data from xdlclass_t
+ xdiff: remove "line_hash" field from xrecord_t
Small clean-up of xdiff library to remove unnecessary data duplication.
Will merge to 'master'.
source: <[email protected]>
* ty/symlinks-use-unsigned-for-bitset (2026-01-21) 1 commit
- symlinks: use unsigned int for flags
Code clean-up.
Expecting a (hopefully small and final) reroll. cf. <[email protected]>
source: <[email protected]>
* ds/revision-maximal-only (2026-01-22) 1 commit
- revision: add --maximal-only option
"git rev-list" and friends learn "--maximal-only" to show only the commits that are not reachable by other commits.
Will merge to 'next'?
source: <[email protected]>
* ng/submodule-default-remote (2026-01-23) 3 commits
- SQUASH??? fixup
- SQUASH??? fixup
- submodule: fetch missing objects from default remote
Instead of hardcoded 'origin', use the configured default remote when fetching from submodules.
Expecting a reroll.
cf. <[email protected]>
source: <[email protected]>
* ar/run-command-hook-take-2 (2026-01-28) 12 commits
- receive-pack: convert receive hooks to hook API
- receive-pack: convert update hooks to new API
- run-command: poll child input in addition to output
- hook: add jobs option
- reference-transaction: use hook API instead of run-command
- transport: convert pre-push to hook API
- hook: allow separate std[out|err] streams
- hook: convert 'post-rewrite' hook in sequencer.c to hook API
- hook: provide stdin via callback
- run-command: add stdin callback for parallelization
- run-command: add helper for pp child states
- t1800: add hook output stream tests
(this branch is used by ar/config-hooks and ar/parallel-hooks.)
Use the hook API to replace ad-hoc invocation of hook scripts via the run_command() API.
Comments?
source: <[email protected]>
* yc/histogram-hunk-shift-fix (2025-12-06) 1 commit
- xdiff: re-diff shifted change groups when using histogram algorithm
The final clean-up phase of the diff output could turn the result of histogram diff algorithm suboptimal, which has been corrected.
Expecting a reroll.
cf. <CAHTeOx-TLwqbcdGcb2drD4vE6D3M93EPMjcAeTNR+XNTbmTVZg@mail.gmail.com>
source: <[email protected]>
* js/neuter-sideband (2026-02-03) 6 commits
- sideband: delay sanitizing by default to Git v3.0
- sideband: offer to configure sanitizing on a per-URL basis
- sideband: add options to allow more control sequences to be passed through
- sideband: do allow ANSI color sequences by default
- sideband: introduce an "escape hatch" to allow control characters
- sideband: mask control characters
Invalidate control characters in sideband messages, to avoid terminal state getting messed up.
Comments?
source: <[email protected]>
* cs/add-skip-submodule-ignore-all (2026-02-06) 5 commits
- Documentation: update add --force option + ignore=all config
- tests: fix existing tests when add an ignore=all submodule
- tests: t2206-add-submodule-ignored: ignore=all and add --force tests
- read-cache: submodule add need --force given ignore=all configuration
- read-cache: update add_files_to_cache take param ignored_too
"git add <submodule>" has been taught to honor submodule.<name>.ignore that is set to "all" (and requires "git add -f" to override it).
Comments?
source: <[email protected]>
* ps/odb-for-each-object (2026-01-26) 16 commits
- odb: drop unused for_each_{loose,packed}_object() functions
- reachable: convert to use odb_for_each_object()
- builtin/pack-objects: use packfile_store_for_each_object()
- odb: introduce mtime fields for object info requests
- treewide: drop uses of for_each_{loose,packed}_object()
- treewide: enumerate promisor objects via odb_for_each_object()
- builtin/fsck: refactor to use odb_for_each_object()
- odb: introduce odb_for_each_object()
- packfile: introduce function to iterate through objects
- packfile: extract function to iterate through objects of a store
- object-file: introduce function to iterate through objects
- object-file: extract function to read object info from path
- odb: fix flags parameter to be unsigned
- odb: rename FOR_EACH_OBJECT_* flags
- Merge branch 'ps/packfile-store-in-odb-source' into ps/odb-for-each-object
- Merge branch 'ps/read-object-info-improvements' into ps/odb-for-each-object
Revamp object enumeration API around odb.
Will merge to 'next'?
cf. <[email protected]>
source: <[email protected]>
* ps/validate-prefix-in-subtree-split (2026-02-03) 1 commit
- subtree: validate --prefix against commit in split
"git subtree split --prefix=P <commit>" now checks the prefix P against the tree of the (potentially quite different from the current working tree) given commit.
Will merge to 'next'?
source: <[email protected]>
* sp/shallow-deepen-relative-fix (2026-01-16) 2 commits
- shallow: handling fetch relative-deepen
- shallow: free local object_array allocations
"git fetch --deepen" that tries to go beyond merged branch used to get confused where the updated shallow points are, which has been corrected.
Comments?
source: <[email protected]>
* ag/http-netrc-tests (2026-01-06) 1 commit
- t5550: add netrc tests for http 401/403
Additional tests were introduced to see the interaction with netrc auth with auth failure on the http transport.
Comments?
source: <[email protected]>
* en/xdiff-cleanup-3 (2026-01-03) 11 commits
. SQUASH??? cocci
. xdiff: move xdl_cleanup_records() from xprepare.c to xdiffi.c . xdiff: remove dependence on xdlclassifier from xdl_cleanup_records() . xdiff: replace xdfile_t.dend with xdfenv_t.delta_end
. xdiff: replace xdfile_t.dstart with xdfenv_t.delta_start . xdiff: cleanup xdl_trim_ends()
. xdiff: use xdfenv_t in xdl_trim_ends() and xdl_cleanup_records() . xdiff: let patience and histogram benefit from xdl_trim_ends() . xdiff: don't waste time guessing the number of lines
. xdiff: make classic diff explicit by creating xdl_do_classic_diff() . ivec: introduce the C side of ivec
Preparation of xdiff/ codebase to work with Rust
Maybe rebase on top of a merge of 'master' with pw/xdiff-cleanups?
source: <[email protected]>
* hn/status-compare-with-push (2026-01-22) 3 commits
- status: add status.compareBranches config for multiple branch comparisons
- refactor format_branch_comparison in preparation
- Merge branch 'jk/remote-tracking-ref-leakfix' into hn/status-compare-with-push
"git status" learned to show comparison between the current branch and its push destination as well as its upstream, when the two are different (i.e., triangular workflow).
What's the status of this topic?
cf. <[email protected]>
source: <[email protected]>
* ob/core-attributesfile-in-repository (2026-02-03) 3 commits
- environment: move "branch.autoSetupMerge" into struct repo_config_values
- environment: stop using core.sparseCheckout globally
- environment: stop storing core.attributesFile globally
The core.attributesfile is intended to be set per repository, but were kept track of by a single global variable in-core, which has been corrected by moving it to per-repository data structure.
Breaks fuzz smoke test.
cf. <[email protected]>
source: <[email protected]>
* pt/fsmonitor-linux (2025-12-31) 1 commit
- fsmonitor: implement filesystem change listener for Linux
The fsmonitor daemon has been implemented for Linux.
Comments?
source: <[email protected]>
* pt/t7527-flake-workaround (2025-12-31) 1 commit
- t7527: fix flaky fsmonitor event tests with retry logic
Test fixup.
Comments?
source: <[email protected]>
* cc/lop-filter-auto (2026-02-12) 9 commits
- fetch-pack: wire up and enable auto filter logic
- promisor-remote: change promisor_remote_reply()'s signature
- promisor-remote: keep advertised filters in memory
- list-objects-filter-options: support 'auto' mode for --filter
- doc: fetch: document --filter=<filter-spec> option
- fetch: make filter_options local to cmd_fetch()
- clone: make filter_options local to cmd_clone()
- promisor-remote: allow a client to store fields
- promisor-remote: refactor initialising field lists
"auto filter" logic for large-object promisor remote.
Will merge to 'next'.
source: <[email protected]>
* tt/receive-pack-oo-namespace-symref-fix (2025-12-27) 1 commit
- receive-pack: fix crash on out-of-namespace symref
"git receive-pack", when namespace is involved, segfaulted when a symbolic ref cross the namespace boundary.
Comments?
source: <[email protected]>
* pc/lockfile-pid (2026-01-22) 1 commit (merged to 'next' on 2026-02-09 at 87bfa08d16)
+ lockfile: add PID file for debugging stale locks
Allow recording process ID of the process that holds the lock next to a lockfile for diagnosis.
Will merge to 'master'.
source: <[email protected]>
* lo/repo-info-keys (2026-01-23) 2 commits
- repo: add new flag --keys to git-repo-info
- repo: rename "keyvalue" to "lines"
"git repo info" learns "--keys" action to list known keys.
Expecting a reroll.
cf. <[email protected]>
source: <[email protected]>
* tb/incremental-midx-part-3.2 (2026-01-14) 19 commits
- midx: enable reachability bitmaps during MIDX compaction
- midx: implement MIDX compaction
- t/helper/test-read-midx.c: plug memory leak when selecting layer
- midx-write.c: factor fanout layering from compute_sorted_entries()
- midx-write.c: enumerate pack_int_id values directly
- midx-write.c: extract fill_pack_from_midx()
- midx-write.c: introduce midx_pack_perm() helper
- git-compat-util.h: introduce u32_add()
- midx: do not require packs to be sorted in lexicographic order
- midx-write.c: introduce struct write_midx_opts
- midx-write.c: don't use pack_perm when assigning bitmap_pos
- t/t5319-multi-pack-index.sh: fix copy-and-paste error in t5319.39
- git-multi-pack-index(1): align SYNOPSIS with 'git multi-pack-index -h'
- git-multi-pack-index(1): remove non-existent incompatibility
- builtin/multi-pack-index.c: make '--progress' a common option
- midx: introduce midx_get_checksum_hex()
- midx: rename get_midx_checksum() to midx_get_checksum_hash()
- midx: mark get_midx_checksum() arguments as const
- Merge branch 'tb/midx-write-corrupt-checksum-fix' into tb/incremental-midx-part-3.2
Further work on incremental repacking using MIDX/bitmap
Comments?
source: <[email protected]>
* bc/sha1-256-interop-02 (2026-02-07) 16 commits
- object-file-convert: always make sure object ID algo is valid
- rust: add a small wrapper around the hashfile code
- rust: add a new binary object map format
- rust: add functionality to hash an object
- rust: add a build.rs script for tests
- rust: fix linking binaries with cargo
- hash: expose hash context functions to Rust
- write-or-die: add an fsync component for the object map
- csum-file: define hashwrite's count as a uint32_t
- rust: add additional helpers for ObjectID
- hash: add a function to look up hash algo structs
- rust: add a hash algorithm abstraction
- rust: add a ObjectID struct
- hash: use uint32_t for object_id algorithm
- conversion: don't crash when no destination algo
- repository: require Rust support for interoperability
The code to maintain mapping between object names in multiple hash functions is being added, written in Rust.
Comments? v1 saw a lot of discussions, v2 didn't, and this is v3, which is essentially identical to v2 with CI fixes (which work!).
source: <[email protected]>
ds/revision-maximal-only (was Re: What's cooking in git.git (Feb 2026, #05))
Quoted 8 lines · Junio C Hamano
* ds/revision-maximal-only (2026-01-22) 1 commit
- revision: add --maximal-only option"git rev-list" and friends learn "--maximal-only" to show only the commits that are not reachable by other commits.
Will merge to 'next'?
source: <[email protected]>
This has been stable for a few weeks, so I think it's ready for 'next'.
Thanks,
-Stolee
Quoted 9 lines · Junio C Hamano
* ps/pack-concat-wo-backfill (2026-02-11) 1 commit
- builtin/pack-objects: don't fetch objects when merging packs"git pack-objects --stdin-packs" with "--exclude-promisor-objects" fetched objects that are promised, which was not wanted. This has been fixed.
Will merge to 'next'?
source: <20260211-pks-pack-objects-stdin-skip-backfill-fetch-v1-1-870cad56d8ae@pks.im>
Yeah, all the reviews have been favorable here, so I think this is ready for next.
Quoted 7 lines
* jc/doc-cg-needswork (2026-02-12) 1 commit
- CodingGuidelines: document NEEDSWORK commentsA CodingGuidelines update.
Will merge to 'next'?
source: <[email protected]>
There's still the one grammar issue pointed out in [1], but once that's fixed I think it can be merged.
Quoted 11 lines
* ps/history-ergonomics-updates (2026-02-13) 5 commits
-Documentation/git-history: document default for "--update-refs="
- builtin/history: rename "--ref-action=" to "--update-refs="
- builtin/history: replace "--ref-action=print" with "--dry-run"
- builtin/history: check for merges before asking for user input
- builtin/history: perform revwalk checks before asking for user inputUI improvements for "git history reword".
Will merge to 'next'?
source: <[email protected]>
I've sent out v3 to fix up a small typo here.
Quoted 8 lines
* ps/meson-gitk-git-gui (2026-02-04) 1 commit
- meson: wire up gitk and git-guiPlumb gitk/git-gui build and install procedure in meson based builds.
Expecting a pull request for gitk.
source: <[email protected]>
That PR for gitk has been merged now. The build for git-gui still has some issues (e.g. no askyesno helper), and fixes for this are in review upstream [2]. I think it's fine to merge this regardless as it won't cause builds to fail, but I'm also happy to wait for the git-gui bits to settle first.
Quoted 11 lines
* jc/checkout-switch-restore (2026-01-29) 2 commits
- checkout: tell "parse_remote_branch" which command is calling it
- checkout: pass program-readable token to unified "main""git switch <name>", in an attempt to create a local branch <name> after a remote tracking branch of the same name gave an advise message to disambiguate using "git checkout", which has been updated to use "git switch".
Will merge to 'next'?
source: <[email protected]>
I think this is good to go.
Quoted 6 lines
* ps/for-each-ref-in-fixes (2026-02-05) 4 commits
- bisect: simplifystring_listmemory handling
- bisect: fix misuse ofrefs_for_each_ref_in()
- pack-bitmap: fix bug with exact ref match in "pack.preferBitmapTips"
- pack-bitmap: deduplicate logic to iterate over preferred bitmap tips
Quoted 6 lines
A handful of places used
refs_for_each_ref_in()API incorrectly, which has been corrected.Will merge to 'next'?
cf. <[email protected]>
source: <20260206-b4-pks-fix-for-each-ref-in-misuse-v3-0-1e050c3d6a50@pks.im>
This has been cooking for a while, and the latest version did address all feedback. So maybe it's time to merge this down now.
Quoted 7 lines
* ps/object-info-bits-cleanup (2026-02-11) 5 commits
- odb: convertodb_has_object()flags into an enum
- odb: convert object info flags into an enum
- odb: drop gaps in object info flag values
- builtin/fsck: fix flags passed toodb_has_object()
- builtin/backfill: fix flags passed toodb_has_object()
Quoted 5 lines
A couple of bugs in use of flag bits around odb API has been corrected, and the flag bits reordered.
Will merge to 'next'?
source: <[email protected]>
Fine with me.
Quoted 18 lines
* ps/odb-for-each-object (2026-01-26) 16 commits
- odb: drop unusedfor_each_{loose,packed}_object()functions
- reachable: convert to useodb_for_each_object()
- builtin/pack-objects: usepackfile_store_for_each_object()
- odb: introduce mtime fields for object info requests
- treewide: drop uses offor_each_{loose,packed}_object()
- treewide: enumerate promisor objects viaodb_for_each_object()
- builtin/fsck: refactor to useodb_for_each_object()
- odb: introduceodb_for_each_object()
- packfile: introduce function to iterate through objects
- packfile: extract function to iterate through objects of a store
- object-file: introduce function to iterate through objects
- object-file: extract function to read object info from path
- odb: fix flags parameter to be unsigned
- odb: renameFOR_EACH_OBJECT_*flags
- Merge branch 'ps/packfile-store-in-odb-source' into ps/odb-for-each-object
- Merge branch 'ps/read-object-info-improvements' into ps/odb-for-each-object
Quoted 5 lines
Revamp object enumeration API around odb.
Will merge to 'next'?
cf. <[email protected]>
source: <[email protected]>
Same here, this has been cooking for a long time by now, and the discussion around mtime has stalled after I clarified intentions and future plans to evolve it further. So I'd love to see this merged.
Thanks!
Patrick
[1]: <[email protected]>
[2]: https://github.com/j6t/git-gui/pull/31
Re: ds/revision-maximal-only (was Re: What's cooking in git.git (Feb 2026, #05))
In reply to Derrick StoleeQuoted 5 lines · Derrick Stolee
Quoted 3 lines · Junio C Hamano
* ds/revision-maximal-only (2026-01-22) 1 commit
- revision: add --maximal-only option
Quoted 8 lines
Quoted 5 lines
"git rev-list" and friends learn "--maximal-only" to show only the commits that are not reachable by other commits.
Will merge to 'next'?
source: <[email protected]>This has been stable for a few weeks, so I think it's ready for 'next'.
I am not 100% sure if "stable" is the most appropriate word to describe the topic, or if it is "dormant". Let's merge it down.
Thanks.