{"thread":{"id":"64873","subject":"What's cooking in git.git (Jan 2026, #09)","startedAt":"2026-01-27T17:42:02Z","lastAt":"2026-02-06T19:39:03Z","messageCount":8,"participants":["Junio C Hamano","Taylor Blau","Derrick Stolee","brian m. carlson","Eric Sunshine"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"534719","messageId":"xmqqecnbeyvr.fsf@gitster.g","threadId":"64873","inReplyTo":null,"subject":"What's cooking in git.git (Jan 2026, #09)","fromName":"Junio C Hamano","fromEmail":"junio@pobox.com","sentAt":"2026-01-27T17:42:00Z","receivedAt":"2026-01-27T17:42:02Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Here are the topics that have been cooking in my tree. Commits\nprefixed with '+' are in 'next' (being in 'next' is a sign that a\ntopic is stable enough to be used and are candidate to be in a\nfuture release). Commits prefixed with '-' are only in 'seen', and\naren't considered \"accepted\" at all and may be annotated with an URL\nto a message that raises issues but they are no means exhaustive. A\ntopic without enough support may be discarded after a long period of\nno activity (of course they can be resubmit when new interests\narise).\n\nCopies of the source code to Git live in many repositories, and the\nfollowing is a list of the ones I push into or their mirrors. Some\nrepositories have only a subset of branches.\n\nGit 2.53-rc2 has been tagged, with one topic reverted recently due\nto a regression. Please keep hunting for regressions.\n\nWith maint, master, next, seen, todo:\n\n\tgit://git.kernel.org/pub/scm/git/git.git/\n\tgit://repo.or.cz/alt-git.git/\n\thttps://kernel.googlesource.com/pub/scm/git/git/\n\thttps://github.com/git/git/\n\thttps://gitlab.com/git-scm/git/\n\nWith all the integration branches and topics broken out:\n\n\thttps://github.com/gitster/git/\n\nEven though the preformatted documentation in HTML and man format\nare not sources, they are published in these repositories for\nconvenience (replace \"htmldocs\" with \"manpages\" for the manual\npages):\n\n\tgit://git.kernel.org/pub/scm/git/git-htmldocs.git/\n\thttps://github.com/gitster/git-htmldocs.git/\n\nRelease tarballs are available at:\n\n\thttps://www.kernel.org/pub/software/scm/git/\n\n--------------------------------------------------\n[New Topics]\n\n* ja/doc-synopsis-style-even-more (2026-01-26) 4 commits\n - doc: convert git-show to synopsis style\n - doc: fix some style issues in git-clone and for-each-ref-options\n - doc: finalize git-clone documentation conversion to synopsis style\n - convert git-submodule doc to synopsis style\n\n A handful of documentation pages have been modernized to use the\n \"synopsis\" style.\n\n Will merge to 'next'?\n source: \n\n\n* ac/string-list-sort-u-and-tests (2026-01-26) 2 commits\n - string-list: add string_list_sort_u() that mimics \"sort -u\"\n - u-string-list: add unit tests for string-list methods\n\n The string_list API gains a new helper, string_list_sort_u(), and\n new unit tests to extend coverage.\n\n Will merge to 'next'.\n source: <20260126185604.90089-1-amishhhaaaa@gmail.com>\n\n\n* ps/object-info-bits-cleanup (2026-01-26) 3 commits\n - odb: drop gaps in object info flag values\n - builtin/fsck: fix flags passed to `odb_has_object()`\n - builtin/backfill: fix flags passed to `odb_has_object()`\n\n A couple of bugs in use of flag bits around odb API has been\n corrected, and the flag bits reordered.\n\n Comments?\n source: <20260126-b4-pks-read-object-info-flags-v1-0-e682a003b17c@pks.im>\n\n\n* pw/xdiff-cleanups (2026-01-26) 2 commits\n - xdiff: remove unused data from xdlclass_t\n - xdiff: remove \"line_hash\" field from xrecord_t\n\n Small clean-up of xdiff library to remove unnecessary data\n duplication.\n\n Comments?\n This conflicts with en/xdiff-cleanup-3 that has been dormant for some time.\n source: \n\n--------------------------------------------------\n[Graduated to 'master']\n\n* dk/replay-doc-omit-irrelevant-rev-list-options (2026-01-21) 2 commits\n (merged to 'next' on 2026-01-21 at a17b449304)\n + lint-gitlink: preemptively ignore all /ifn?def|endif/ macros\n + replay: drop rev-list formatting options from manual\n\n Documentation clean-up.\n source: <01a7acfaf87494419b3766da57d4c05cf99c79bb.1768873599.git.ben.knoble+github@gmail.com>\n\n\n* js/ci-leak-skip-svn (2026-01-17) 2 commits\n (merged to 'next' on 2026-01-21 at ebcf21d088)\n + ci: skip CVS and P4 tests in leaks job, too\n + ci(*-leaks): skip the git-svn tests to save time\n\n Dscho observed that SVN tests are taking too much time in CI leak\n checking tasks, but most time is spent not in our code but in libsvn\n code (which happen to be written in Perl), whose leaks have little\n value to discover for us. Skip SVN, P4, and CVS tests in the leak\n checking tasks.\n source: \n\n\n* js/symlink-windows (2026-01-09) 19 commits\n (merged to 'next' on 2026-01-21 at eaaead3f22)\n + mingw: special-case index entries for symlinks with buggy size\n + mingw: emulate `stat()` a little more faithfully\n + mingw: try to create symlinks without elevated permissions\n + mingw: add support for symlinks to directories\n + mingw: implement basic `symlink()` functionality (file symlinks only)\n + mingw: implement `readlink()`\n + mingw: allow `mingw_chdir()` to change to symlink-resolved directories\n + mingw: support renaming symlinks\n + mingw: handle symlinks to directories in `mingw_unlink()`\n + mingw: add symlink-specific error codes\n + mingw: change default of `core.symlinks` to false\n + mingw: factor out the retry logic\n + mingw: compute the correct size for symlinks in `mingw_lstat()`\n + mingw: teach dirent about symlinks\n + mingw: let `mingw_lstat()` error early upon problems with reparse points\n + mingw: drop the separate `do_lstat()` function\n + mingw: implement `stat()` with symlink support\n + mingw: don't call `GetFileAttributes()` twice in `mingw_lstat()`\n + Merge branch 'js/prep-symlink-windows' into js/symlink-windows\n\n Upstream symbolic link support on Windows from Git-for-Windows.\n source: \n\n\n* jx/build-options-gettext (2026-01-17) 1 commit\n (merged to 'next' on 2026-01-21 at dd35ac2e2a)\n + help: report on whether or not gettext is enabled\n\n \"git bugreport\" and \"git version --build-options\" learned to\n include use of 'gettext' feature, to make it easier to diagnose\n problems around l10n.\n source: <251e1b533ca2e38a9bedae44360ce636cdea4bc3.1768657640.git.zhiyou.jx@alibaba-inc.com>\n\n\n* kh/mailmap-avila (2026-01-21) 1 commit\n (merged to 'next' on 2026-01-22 at d81095ad13)\n + .mailmap: fix and expand mappings for Jean-Noël Avila\n\n Will merge to 'master'.\n source: \n\n\n* pw/mailmap-self (2026-01-20) 1 commit\n (merged to 'next' on 2026-01-21 at da7d118d77)\n + mailmap: add an entry for Phillip Wood\n\n Unify entries in .mailmap file for Phillip Wood.\n source: \n\n\n* rj/cygwin-test-fixes-for-2.53 (2026-01-16) 2 commits\n (merged to 'next' on 2026-01-21 at 8a1ed2cace)\n + t0610-reftable-basics: mitigate a flaky test on cygwin\n + t9700/test.pl: fix path type expectation on cygwin\n\n Test fixup.\n source: \n\n\n* sb/doc-update-ref-markup-fix (2025-12-08) 1 commit\n (merged to 'next' on 2026-01-21 at 60d4750233)\n + doc: fix `update-ref` `symref-create` formatting\n\n Doc mark-up fix.\n source: \n\n\n* ty/t1005-test-path-is-helpers (2026-01-16) 1 commit\n (merged to 'next' on 2026-01-21 at 690bb3b255)\n + t1005: modernize \"! test -f\" to \"test_path_is_missing\"\n\n Test clean-up.\n source: <20260117062515.319664-1-a3205153416@gmail.com>\n\n--------------------------------------------------\n[Cooking]\n\n* sp/t5500-cleanup (2026-01-21) 1 commit\n (merged to 'next' on 2026-01-23 at d5adc61ce8)\n + t5500: simplify test implementation and fix git exit code suppression\n\n Test clean-up.\n\n Will cook in 'next'.\n source: <20260121130012.888299-1-shreyanshpaliwalcmsmn@gmail.com>\n\n\n* ty/symlinks-use-unsigned-for-bitset (2026-01-21) 1 commit\n - symlinks: use unsigned int for flags\n\n Code clean-up.\n\n Expecting a (hopefully small and final) reroll.\n cf. \n source: <20260121162640.424126-1-a3205153416@gmail.com>\n\n\n* ds/revision-maximal-only (2026-01-22) 1 commit\n - revision: add --maximal-only option\n\n \"git rev-list\" and friends learn \"--maximal-only\" to show only the\n commits that are not reachable by other commits.\n\n Will merge to 'next'?\n source: \n\n\n* ng/submodule-default-remote (2026-01-23) 3 commits\n - SQUASH??? fixup\n - SQUASH??? fixup\n - submodule: fetch missing objects from default remote\n\n Instead of hardcoded 'origin', use the configured default remote\n when fetching from submodules.\n\n Expecting a review response.\n source: <20260122152722.866341-1-nasser.grainawi@oss.qualcomm.com>\n\n\n* ar/run-command-hook-take-2 (2026-01-21) 12 commits\n - receive-pack: convert receive hooks to hook API\n - receive-pack: convert update hooks to new API\n - run-command: poll child stdin in addition to stdout\n - hook: add jobs option\n - reference-transaction: use hook API instead of run-command\n - transport: convert pre-push to hook API\n - hook: allow separate std[out|err] streams\n - hook: convert 'post-rewrite' hook in sequencer.c to hook API\n - hook: provide stdin via callback\n - run-command: add stdin callback for parallelization\n - run-command: add first helper for pp child states\n - t1800: add hook output stream tests\n\n Use the hook API to replace ad-hoc invocation of hook scripts via\n the run_command() API.\n\n Expecting a reroll.\n cf. <87cy32q9qh.fsf@collabora.com>\n source: <20260121215436.1473800-1-adrian.ratiu@collabora.com>\n\n\n* lp/diff-stat-utf8-display-width-fix (2026-01-15) 2 commits\n (merged to 'next' on 2026-01-23 at 80e7ddce3e)\n + t4073: add test for diffstat paths length when containing UTF-8 chars\n + diff: improve scaling of filenames in diffstat to handle UTF-8 chars\n\n The computation of column width made by \"git diff --stat\" was\n confused when pathnames contain non-ASCII characters.\n\n Will cook in 'next'.\n source: \n\n\n* jk/remote-tracking-ref-leakfix (2026-01-18) 4 commits\n (merged to 'next' on 2026-01-21 at 7f0736a973)\n + remote: always allocate branch.push_tracking_ref\n + remote: fix leak in branch_get_push_1() with invalid \"simple\" config\n + remote: drop const return of tracking_for_push_dest()\n + remote: return non-const pointer from error_buf()\n (this branch is used by hn/status-compare-with-push.)\n\n Leakfix.\n\n Will cook in 'next'.\n source: <20260119051858.GA1991308@coredump.intra.peff.net>\n\n\n* yc/histogram-hunk-shift-fix (2025-12-06) 1 commit\n - xdiff: re-diff shifted change groups when using histogram algorithm\n\n The final clean-up phase of the diff output could turn the result of\n histogram diff algorithm suboptimal, which has been corrected.\n\n Expecting a review response.\n cf. <4fa413ae-f2a4-4de2-a2fb-0b1db379750b@gmail.com>\n source: \n\n\n* js/neuter-sideband (2026-01-16) 5 commits\n - sideband: offer to configure sanitizing on a per-URL basis\n - sideband: add options to allow more control sequences to be passed through\n - sideband: do allow ANSI color sequences by default\n - sideband: introduce an \"escape hatch\" to allow control characters\n - sideband: mask control characters\n\n Invalidate control characters in sideband messages, to avoid\n terminal state getting messed up.\n\n Expecting a reroll to make things opt-in, not opt-out.\n source: \n\n\n* tc/last-modified-options-cleanup (2026-01-20) 4 commits\n (merged to 'next' on 2026-01-23 at e514d98b11)\n + last-modified: change default max-depth to 0\n + last-modified: document option '--max-depth'\n + last-modified: document option '-z'\n + last-modified: clarify in the docs the command takes a pathspec\n\n The \"-z\" and \"--max-depth\" documentation (and implementation of\n \"-z\") in the \"git last-modified\" command have been updated.\n\n Will cook in 'next'.\n source: <20260120-toon-last-modified-zzzz-v3-0-9bffd4968b0e@iotcl.com>\n\n\n* tc/last-modified-not-a-tree (2026-01-23) 4 commits\n - last-modified: verify revision argument is a commit-ish\n - last-modified: remove double error message\n - last-modified: fix memory leak when more than one revision is given\n - last-modified: rewrite error message when more than one revision given\n\n Giving \"git last-modified\" a tree (not a commit-ish) died an\n uncontrolled death, which has been corrected.\n\n Expecting a reroll.\n cf. \n source: <20260123-toon-last-modified-tree-v4-0-86bf97bad4e2@iotcl.com>\n\n\n* sp/myfirstcontribution-include-update (2026-01-12) 1 commit\n (merged to 'next' on 2026-01-23 at 2d039d03ff)\n + doc: MyFirstContribution: fix missing dependencies and clarify build steps\n\n Doc update.\n\n Will cook in 'next'.\n source: <20260112195625.391821-1-shreyanshpaliwalcmsmn@gmail.com>\n\n\n* cs/add-skip-submodule-ignore-all (2026-01-13) 5 commits\n - Documentation: update add --force option + ignore=all config\n - tests: fix existing tests when add an ignore=all submodule\n - tests: t2206-add-submodule-ignored: ignore=all and add --force tests\n - read-cache: submodule add need --force given ignore=all configuration\n - read-cache: update add_files_to_cache take param ignored_too\n\n \"git add \" has been taught to honor\n submodule..ignore that is set to \"all\" (and requires \"git add\n -f\" to override it).\n\n Expecting a reroll.\n cf. \n cf. \n source: <37fe7956e089394bb1d75f4c8af4a3347b204803.1768376879.git.gitgitgadget@gmail.com>\n\n\n* kn/ref-batch-output-error-reporting-fix (2026-01-25) 6 commits\n - fetch: delay user information post committing of transaction\n - receive-pack: utilize rejected ref error details\n - fetch: utilize rejected ref error details\n - update-ref: utilize rejected error details if available\n - refs: add rejection detail to the callback function\n - refs: skip to next ref when current ref is rejected\n\n A handful of code paths that started using batched ref update API\n (after Git 2.51 or so) lost detailed error output, which have been\n corrected.\n\n Will merge to 'next'?\n source: <20260125-633-regression-lost-diagnostic-message-when-pushing-non-commit-objects-to-refs-heads-v5-0-d58f3a9edf98@gmail.com>\n\n\n* ac/sparse-checkout-string-list-cleanup (2026-01-21) 1 commit\n (merged to 'next' on 2026-01-23 at 885244a10d)\n + sparse-checkout: optimize string_list construction and add tests to verify deduplication.\n\n Code clean-up.\n\n Will cook in 'next'.\n source: <20260121130005.72375-1-amishhhaaaa@gmail.com>\n\n\n* ps/commit-list-functions-renamed (2026-01-15) 3 commits\n - commit: rename `free_commit_list()` to conform to coding guidelines\n - commit: rename `reverse_commit_list()` to conform to coding guidelines\n - commit: rename `copy_commit_list()` to conform to coding guidelines\n\n Rename three functions around the commit_list data structure.\n\n Will merge to 'next'?\n source: <20260115-pks-commit-list-coding-guidelines-v1-0-c58868dbf412@pks.im>\n\n\n* ps/odb-for-each-object (2026-01-26) 16 commits\n - odb: drop unused `for_each_{loose,packed}_object()` functions\n - reachable: convert to use `odb_for_each_object()`\n - builtin/pack-objects: use `packfile_store_for_each_object()`\n - odb: introduce mtime fields for object info requests\n - treewide: drop uses of `for_each_{loose,packed}_object()`\n - treewide: enumerate promisor objects via `odb_for_each_object()`\n - builtin/fsck: refactor to use `odb_for_each_object()`\n - odb: introduce `odb_for_each_object()`\n - packfile: introduce function to iterate through objects\n - packfile: extract function to iterate through objects of a store\n - object-file: introduce function to iterate through objects\n - object-file: extract function to read object info from path\n - odb: fix flags parameter to be unsigned\n - odb: rename `FOR_EACH_OBJECT_*` flags\n - Merge branch 'ps/packfile-store-in-odb-source' into ps/odb-for-each-object\n - Merge branch 'ps/read-object-info-improvements' into ps/odb-for-each-object\n\n Revamp object enumeration API around odb.\n\n Will merge to 'next'?\n source: <20260126-pks-odb-for-each-object-v4-0-5a64a038c791@pks.im>\n\n\n* ps/validate-prefix-in-subtree-split (2026-01-15) 1 commit\n - subtree: validate --prefix against commit in split\n\n \"git subtree split --prefix=P \" now checks the prefix P\n against the tree of the (potentially quite different from the\n current working tree) given commit.\n\n Expecting a reroll?\n source: <20260115122652.18673-2-pushkarkumarsingh1970@gmail.com>\n\n\n* sp/shallow-deepen-relative-fix (2026-01-16) 2 commits\n - shallow: handling fetch relative-deepen\n - shallow: free local object_array allocations\n\n \"git fetch --deepen\" that tries to go beyond merged branch used to\n get confused where the updated shallow points are, which has been\n corrected.\n\n Comments?\n source: \n\n\n* dd/t5403-modernise (2026-01-12) 2 commits\n (merged to 'next' on 2026-01-23 at ca3ceb637e)\n + t5403: use test_cmp for post-checkout argument checks\n + t5403: introduce check_post_checkout helper function\n\n Test clean-up.\n\n Will cook in 'next'.\n\n\n* ag/http-netrc-tests (2026-01-06) 1 commit\n - t5550: add netrc tests for http 401/403\n\n Additional tests were introduced to see the interaction with netrc\n auth with auth failure on the http transport.\n\n Comments?\n source: <20260106114029.763351-1-git@ashlesh.me>\n\n\n* en/xdiff-cleanup-3 (2026-01-03) 11 commits\n . SQUASH??? cocci\n . xdiff: move xdl_cleanup_records() from xprepare.c to xdiffi.c\n . xdiff: remove dependence on xdlclassifier from xdl_cleanup_records()\n . xdiff: replace xdfile_t.dend with xdfenv_t.delta_end\n . xdiff: replace xdfile_t.dstart with xdfenv_t.delta_start\n . xdiff: cleanup xdl_trim_ends()\n . xdiff: use xdfenv_t in xdl_trim_ends() and xdl_cleanup_records()\n . xdiff: let patience and histogram benefit from xdl_trim_ends()\n . xdiff: don't waste time guessing the number of lines\n . xdiff: make classic diff explicit by creating xdl_do_classic_diff()\n . ivec: introduce the C side of ivec\n\n Preparation of xdiff/ codebase to work with Rust\n\n What's the status of this one?\n source: \n\n\n* hn/status-compare-with-push (2026-01-22) 3 commits\n - status: add status.compareBranches config for multiple branch comparisons\n - refactor format_branch_comparison in preparation\n - Merge branch 'jk/remote-tracking-ref-leakfix' into hn/status-compare-with-push\n (this branch uses jk/remote-tracking-ref-leakfix.)\n\n \"git status\" learned to show comparison between the current branch\n and its push destination as well as its upstream, when the two are\n different (i.e., triangular workflow).\n\n Under further discussion?\n cf. <20260122220154.GA2107958@coredump.intra.peff.net>\n source: \n\n\n* ob/core-attributesfile-in-repository (2026-01-24) 3 commits\n - environment: move \"branch.autoSetupMerge\" into `struct repo_config_values`\n - environment: stop using core.sparseCheckout globally\n - environment: stop storing `core.attributesFile` globally\n\n The core.attributesfile is intended to be set per repository, but\n were kept track of by a single global variable in-core, which has\n been corrected by moving it to per-repository data structure.\n\n Comments?\n source: \n\n\n* aa/add-p-previous-decisions (2026-01-08) 1 commit\n (merged to 'next' on 2026-01-21 at 4e2fe2bd9b)\n + add -p: show user's hunk decision when selecting hunks\n\n \"git add -p\" and friends notes what the current status of the hunk\n being shown is.\n\n Will cook in 'next'.\n source: \n\n\n* pt/fsmonitor-linux (2025-12-31) 1 commit\n - fsmonitor: implement filesystem change listener for Linux\n\n The fsmonitor daemon has been implemented for Linux.\n\n Comments?\n source: \n\n\n* pt/t7527-flake-workaround (2025-12-31) 1 commit\n - t7527: fix flaky fsmonitor event tests with retry logic\n\n Test fixup.\n\n Comments?\n source: \n\n\n* cc/lop-filter-auto (2025-12-23) 9 commits\n - fetch-pack: wire up and enable auto filter logic\n - promisor-remote: keep advertised filter in memory\n - list-objects-filter-options: implement auto filter resolution\n - list-objects-filter-options: support 'auto' mode for --filter\n - doc: fetch: document `--filter=` option\n - fetch: make filter_options local to cmd_fetch()\n - clone: make filter_options local to cmd_clone()\n - promisor-remote: allow a client to store fields\n - promisor-remote: refactor initialising field lists\n\n \"auto filter\" logic for large-object promisor remote.\n\n Comments?\n source: <20251223111113.47473-1-christian.couder@gmail.com>\n\n\n* tt/receive-pack-oo-namespace-symref-fix (2025-12-27) 1 commit\n - receive-pack: fix crash on out-of-namespace symref\n\n \"git receive-pack\", when namespace is involved, segfaulted when a\n symbolic ref cross the namespace boundary.\n\n Comments?\n source: \n\n\n* sb/doc-worktree-prune-expire-improvement (2025-12-19) 2 commits\n - worktree: use 'prune' instead of 'expire' in help text\n - worktree: clarify --expire applies to missing worktrees\n\n The help text and the documentation for the \"--expire\" option of\n \"git worktree [list|prune]\" have been improved.\n\n Expecting a reroll.\n source: \n\n\n* pc/lockfile-pid (2026-01-22) 1 commit\n - lockfile: add PID file for debugging stale locks\n\n Allow recording process ID of the process that holds the lock next\n to a lockfile for diagnosis.\n\n Will mrge to 'next'?\n source: \n\n\n* ap/http-probe-rpc-use-auth (2026-01-14) 1 commit\n (merged to 'next' on 2026-01-23 at 0439366395)\n + remote-curl: use auth for probe_rpc() requests too\n\n HTTP transport failed to authenticate in some code paths, which has\n been corrected.\n\n Will cook in 'next'.\n source: <20260114163619.614297-2-aplattner@nvidia.com>\n\n\n* lo/repo-info-keys (2026-01-23) 2 commits\n - repo: add new flag --keys to git-repo-info\n - repo: rename \"keyvalue\" to \"lines\"\n\n \"git repo info\" learns \"--keys\" action to list known keys.\n\n Comments?\n source: <20260123164900.35092-1-lucasseikioshiro@gmail.com>\n\n\n* tb/incremental-midx-part-3.2 (2026-01-14) 19 commits\n - midx: enable reachability bitmaps during MIDX compaction\n - midx: implement MIDX compaction\n - t/helper/test-read-midx.c: plug memory leak when selecting layer\n - midx-write.c: factor fanout layering from `compute_sorted_entries()`\n - midx-write.c: enumerate `pack_int_id` values directly\n - midx-write.c: extract `fill_pack_from_midx()`\n - midx-write.c: introduce `midx_pack_perm()` helper\n - git-compat-util.h: introduce `u32_add()`\n - midx: do not require packs to be sorted in lexicographic order\n - midx-write.c: introduce `struct write_midx_opts`\n - midx-write.c: don't use `pack_perm` when assigning `bitmap_pos`\n - t/t5319-multi-pack-index.sh: fix copy-and-paste error in t5319.39\n - git-multi-pack-index(1): align SYNOPSIS with 'git multi-pack-index -h'\n - git-multi-pack-index(1): remove non-existent incompatibility\n - builtin/multi-pack-index.c: make '--progress' a common option\n - midx: introduce `midx_get_checksum_hex()`\n - midx: rename `get_midx_checksum()` to `midx_get_checksum_hash()`\n - midx: mark `get_midx_checksum()` arguments as const\n - Merge branch 'tb/midx-write-corrupt-checksum-fix' into tb/incremental-midx-part-3.2\n\n Further work on incremental repacking using MIDX/bitmap\n\n Comments?\n source: \n\n\n* pw/replay-drop-empty (2025-12-18) 2 commits\n - replay: drop commits that become empty\n - Merge branch 'ps/history' into pw/replay-drop-empty\n (this branch uses ps/history.)\n\n \"git replay\" is taught to drop commits that become empty (not the\n ones that are empty in the original).\n\n Will merge to 'next', together with 'ps/history'?\n source: <375adc4e941f3bb22a2b12ee26a083951ed724dd.1766076625.git.phillip.wood@dunelm.org.uk>\n\n\n* bc/sha1-256-interop-02 (2025-11-17) 15 commits\n - object-file-convert: always make sure object ID algo is valid\n - rust: add a small wrapper around the hashfile code\n - rust: add a new binary object map format\n - rust: add functionality to hash an object\n - rust: add a build.rs script for tests\n - hash: expose hash context functions to Rust\n - write-or-die: add an fsync component for the object map\n - csum-file: define hashwrite's count as a uint32_t\n - rust: add additional helpers for ObjectID\n - hash: add a function to look up hash algo structs\n - rust: add a hash algorithm abstraction\n - rust: add a ObjectID struct\n - hash: use uint32_t for object_id algorithm\n - conversion: don't crash when no destination algo\n - repository: require Rust support for interoperability\n\n The code to maintain mapping between object names in multiple hash\n functions is being added, written in Rust.\n\n Any progress on CI breakages???\n source: <20251117221621.2863243-1-sandals@crustytoothpaste.net>\n\n\n* ps/history (2026-01-13) 9 commits\n - builtin/history: implement \"reword\" subcommand\n - builtin: add new \"history\" command\n - wt-status: provide function to expose status for trees\n - replay: support updating detached HEAD\n - replay: support empty commit ranges\n - replay: small set of cleanups\n - builtin/replay: move core logic into \"libgit.a\"\n - builtin/replay: extract core logic to replay revisions\n - Merge branch 'kh/replay-invalid-onto-advance' into ps/history\n (this branch is used by pw/replay-drop-empty.)\n\n \"git history\" history rewriting UI.\n\n Will merge to 'next'.\n cf. \n cf. \n source: <20260113-b4-pks-history-builtin-v11-0-e74ebfa2652d@pks.im>\n\n\n* ar/submodule-gitdir-tweak (2026-01-12) 11 commits\n (merged to 'next' on 2026-01-23 at ef3c2cab02)\n + submodule: detect conflicts with existing gitdir configs\n + submodule: hash the submodule name for the gitdir path\n + submodule: fix case-folding gitdir filesystem collisions\n + submodule--helper: fix filesystem collisions by encoding gitdir paths\n + builtin/credential-store: move is_rfc3986_unreserved to url.[ch]\n + submodule--helper: add gitdir migration command\n + submodule: allow runtime enabling extensions.submodulePathConfig\n + submodule: introduce extensions.submodulePathConfig\n + builtin/submodule--helper: add gitdir command\n + submodule: always validate gitdirs inside submodule_name_to_gitdir\n + submodule--helper: use submodule_name_to_gitdir in add_submodule\n\n Avoid local submodule repository directory paths overlapping with\n each other by encoding submodule names before using them as path\n components.\n\n Will cook in 'next'.\n cf. \n source: <20260112184632.1334495-1-adrian.ratiu@collabora.com>\n\n--------------------------------------------------\n[Discarded]\n\n* dw/config-global-list (2025-10-09) 4 commits\n . config: keep bailing on unreadable global files\n . config: read global scope via config_sequence\n . config: test home and xdg files in `list --global`\n . cleanup_path: force forward slashes on Windows\n\n \"git config --list --global\", unlike \"git config --list\", did not\n consult both of the two possible per-user sources of the\n configuration files, i.e. $HOME/.gitconfig and the XDG one, which\n has been corrected.\n\n Will discard. Has been waiting for a reroll for too long.\n cf. <20251122020047.GB3947@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>\n cf. \n source: \n\n\n* ms/doc-worktree-side-by-side (2025-10-10) 2 commits\n . doc: git-worktree: Add side by side branch checkout example\n . doc: git-worktree: Link to examples\n\n Document \"git worktree add\" and use of out-of-tree worktrees with\n examples.\n\n Will discard. Has been waiting for a reroll for too long.\n cf. \n cf. \n source: \n\n\n* jc/exclude-with-gitignore (2025-11-04) 1 commit\n . dir.c: do not be fooled by :(exclude) pathspec elements\n\n \"git add ':(exclude)foo.o'\" is clearly a request not to add 'foo.o',\n but the command complained about listing an ignored path foo.o on\n the command line, which has been corrected.\n\n Will discard. Has been waiting for further comments for too long.\n cf. \n source: \n\n\n* lc/rebase-trailer (2025-11-05) 4 commits\n . rebase: support --trailer\n . trailer: append trailers in-process and drop the fork to `interpret-trailers`\n . trailer: move process_trailers to trailer.h\n . interpret-trailers: factor out buffer-based processing to process_trailers()\n\n Refactor code paths to run \"interpret-trailers\" from \"git\n commit/tag\" and use it in \"git rebase\".\n\n Will discard. Has been waiting for a reroll for too long.\n cf. <19a8fe42354.3909481a3912041.7970296104893780556@linux.beauty>\n cf. \n source: <20251105142944.73061-1-me@linux.beauty>\n\n\n* sp/shallow-time-boundary (2025-11-23) 1 commit\n . shallow: set borders which are all reachable after clone shallow since\n\n The set of shallow boundary \"git clone --shallow-since\" leaves\n contained commits that are not on the boundary, which has been\n corrected.\n\n Will discard. Has been waiting for further comments for too long.\n cf. \n source: \n\n\n* jk/parse-int (2025-11-30) 5 commits\n . fsck: use parse_unsigned_from_buf() for parsing timestamp\n . cache-tree: use parse_int_from_buf()\n . parse: add functions for parsing from non-string buffers\n . parse: prefer bool to int for boolean returns\n . Merge branch 'jk/asan-bonanza' into jk/parse-int\n\n Introduce a more robust way to parse a decimal integer stored in a\n piece of memory that is not necessarily terminated with NUL (which\n Asan strict-string-check complains even when use of strtol() is\n safe due to varified existence of whitespace after the digits).\n\n Will discard. Has been waiting for a reroll for too long.\n cf. \n cf. <4d83375b-76e2-4420-80dd-6a04d3201532@gmail.com>\n cf. \n source: <20251130131351.GA198697@coredump.intra.peff.net>\n\n\n* kn/ref-location (2025-12-01) 2 commits\n . refs: add GIT_REF_URI to specify reference backend and directory\n . refs: support obtaining ref_store for given dir\n\n A mechanism to specify what reference backend to use and store\n references in which directory is introduced, which would likely to\n be useful during ref migration.\n\n Will discard. Has been waiting for further comments for too long.\n cf. \n source: <20251201-kn-alternate-ref-dir-v3-0-c11b946bc2fa@gmail.com>\n"},{"id":"534730","messageId":"aXk2FjTUMMThs5Kp@nand.local","threadId":"64873","inReplyTo":"xmqqecnbeyvr.fsf@gitster.g","subject":"Re: What's cooking in git.git (Jan 2026, #09)","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2026-01-27T22:03:02Z","receivedAt":"2026-01-27T22:03:05Z","isPatch":false,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"On Tue, Jan 27, 2026 at 09:42:00AM -0800, Junio C Hamano wrote:\n> * ps/odb-for-each-object (2026-01-26) 16 commits\n> - odb: drop unused `for_each_{loose,packed}_object()` functions\n> - reachable: convert to use `odb_for_each_object()`\n> - builtin/pack-objects: use `packfile_store_for_each_object()`\n> - odb: introduce mtime fields for object info requests\n> - treewide: drop uses of `for_each_{loose,packed}_object()`\n> - treewide: enumerate promisor objects via `odb_for_each_object()`\n> - builtin/fsck: refactor to use `odb_for_each_object()`\n> - odb: introduce `odb_for_each_object()`\n> - packfile: introduce function to iterate through objects\n> - packfile: extract function to iterate through objects of a store\n> - object-file: introduce function to iterate through objects\n> - object-file: extract function to read object info from path\n> - odb: fix flags parameter to be unsigned\n> - odb: rename `FOR_EACH_OBJECT_*` flags\n> - Merge branch 'ps/packfile-store-in-odb-source' into ps/odb-for-each-object\n> - Merge branch 'ps/read-object-info-improvements' into ps/odb-for-each-object\n>\n> Revamp object enumeration API around odb.\n>\n> Will merge to 'next'?\n> source: <20260126-pks-odb-for-each-object-v4-0-5a64a038c791@pks.im>\n\nI have some lingering questions about the mtime-related changes. I am\nnot opposed to the series in general, but I think some more time to\ncontinue the discussion in that thread would be beneficial before\nstarting to merge it down.\n\nThanks,\nTaylor\n"},{"id":"534764","messageId":"283c6bc4-787d-4035-bc94-a85ca775e8f0@gmail.com","threadId":"64873","inReplyTo":"xmqqecnbeyvr.fsf@gitster.g","subject":"ds/revision-maximal-only (was Re: What's cooking in git.git (Jan 2026, #09))","fromName":"Derrick Stolee","fromEmail":"stolee@gmail.com","sentAt":"2026-01-28T14:29:29Z","receivedAt":"2026-01-28T14:29:31Z","isPatch":false,"sender":{"key":"stolee@gmail.com","avatar":"https://avatars.githubusercontent.com/u/570044?v=4"},"body":"On 1/27/26 12:42 PM, Junio C Hamano wrote:\n> * ds/revision-maximal-only (2026-01-22) 1 commit\n> - revision: add --maximal-only option\n> \n> \"git rev-list\" and friends learn \"--maximal-only\" to show only the\n> commits that are not reachable by other commits.\n> \n> Will merge to 'next'?\n> source: \n\nI believe that the discussion has landed in a place where this version\nis good to merge. Any remaining discussions around using the 'git\nmerge-base --independent' algorithm when appropriate or adding\n'--maximal-only' to other builtins can be delayed to a future\nextension, I think.\n\nThanks,\n-Stolee\n\n\n"},{"id":"534786","messageId":"aXqSyn3Mfcgs8MUG@fruit.crustytoothpaste.net","threadId":"64873","inReplyTo":"xmqqecnbeyvr.fsf@gitster.g","subject":"Re: What's cooking in git.git (Jan 2026, #09)","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2026-01-28T22:50:50Z","receivedAt":"2026-01-28T22:50:53Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2026-01-27 at 17:42:00, Junio C Hamano wrote:\n> * bc/sha1-256-interop-02 (2025-11-17) 15 commits\n> - object-file-convert: always make sure object ID algo is valid\n> - rust: add a small wrapper around the hashfile code\n> - rust: add a new binary object map format\n> - rust: add functionality to hash an object\n> - rust: add a build.rs script for tests\n> - hash: expose hash context functions to Rust\n> - write-or-die: add an fsync component for the object map\n> - csum-file: define hashwrite's count as a uint32_t\n> - rust: add additional helpers for ObjectID\n> - hash: add a function to look up hash algo structs\n> - rust: add a hash algorithm abstraction\n> - rust: add a ObjectID struct\n> - hash: use uint32_t for object_id algorithm\n> - conversion: don't crash when no destination algo\n> - repository: require Rust support for interoperability\n> \n> The code to maintain mapping between object names in multiple hash\n> functions is being added, written in Rust.\n> \n> Any progress on CI breakages???\n> source: <20251117221621.2863243-1-sandals@crustytoothpaste.net>\n\nNot yet, but I hope to spend some time on that this week or early next.\nI now have some more time to work on this at work and I can try to poke\naround and figure out what might be wrong, or at least try to beg a\ncolleague to try things on their Windows VM.\n\nMy apologies for the delay; things have been busy lately and I've had\nless personal time to work on Git.\n-- \nbrian m. carlson (they/them)\nToronto, Ontario, CA\n"},{"id":"534841","messageId":"aXvYnCsXPV0yefyD@fruit.crustytoothpaste.net","threadId":"64873","inReplyTo":"aXqSyn3Mfcgs8MUG@fruit.crustytoothpaste.net","subject":"Re: What's cooking in git.git (Jan 2026, #09)","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2026-01-29T22:01:00Z","receivedAt":"2026-01-29T22:01:09Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2026-01-28 at 22:50:50, brian m. carlson wrote:\n> On 2026-01-27 at 17:42:00, Junio C Hamano wrote:\n> > * bc/sha1-256-interop-02 (2025-11-17) 15 commits\n> > - object-file-convert: always make sure object ID algo is valid\n> > - rust: add a small wrapper around the hashfile code\n> > - rust: add a new binary object map format\n> > - rust: add functionality to hash an object\n> > - rust: add a build.rs script for tests\n> > - hash: expose hash context functions to Rust\n> > - write-or-die: add an fsync component for the object map\n> > - csum-file: define hashwrite's count as a uint32_t\n> > - rust: add additional helpers for ObjectID\n> > - hash: add a function to look up hash algo structs\n> > - rust: add a hash algorithm abstraction\n> > - rust: add a ObjectID struct\n> > - hash: use uint32_t for object_id algorithm\n> > - conversion: don't crash when no destination algo\n> > - repository: require Rust support for interoperability\n> > \n> > The code to maintain mapping between object names in multiple hash\n> > functions is being added, written in Rust.\n> > \n> > Any progress on CI breakages???\n> > source: <20251117221621.2863243-1-sandals@crustytoothpaste.net>\n> \n> Not yet, but I hope to spend some time on that this week or early next.\n> I now have some more time to work on this at work and I can try to poke\n> around and figure out what might be wrong, or at least try to beg a\n> colleague to try things on their Windows VM.\n\nI did not get a Windows VM working but I did discover the problem and\nI'm working on a patch and will send it out once I have CI green.\n\nThe problem is roughly that both the MSVC linker and MSYS linker are\nboth called link.exe. When compiling with Rust against MSVC, the MSVC\nlinker must be used, but the MSYS linker is first in PATH (because I\nbelieve installing the Git for Windows SDK causes that to be the case),\ncausing build.rs to fail to compile.\n-- \nbrian m. carlson (they/them)\nToronto, Ontario, CA\n"},{"id":"534842","messageId":"CAPig+cStjN15WEKSN3b5VGLK-+N5pzj-dUDQ2rm15ne_9Q07FQ@mail.gmail.com","threadId":"64873","inReplyTo":"aXvYnCsXPV0yefyD@fruit.crustytoothpaste.net","subject":"Re: What's cooking in git.git (Jan 2026, #09)","fromName":"Eric Sunshine","fromEmail":"ericsunshine@gmail.com","sentAt":"2026-01-29T22:51:40Z","receivedAt":"2026-01-29T22:51:53Z","isPatch":false,"sender":{"key":"ericsunshine@gmail.com","avatar":null},"body":"On Thu, Jan 29, 2026 at 5:01 PM brian m. carlson\n wrote:\n> On 2026-01-28 at 22:50:50, brian m. carlson wrote:\n> > On 2026-01-27 at 17:42:00, Junio C Hamano wrote:\n> > > * bc/sha1-256-interop-02 (2025-11-17) 15 commits\n> > >\n> > > The code to maintain mapping between object names in multiple hash\n> > > functions is being added, written in Rust.\n> > >\n> > > Any progress on CI breakages???\n> >\n> > Not yet, but I hope to spend some time on that this week or early next.\n> > I now have some more time to work on this at work and I can try to poke\n> > around and figure out what might be wrong, or at least try to beg a\n> > colleague to try things on their Windows VM.\n>\n> I did not get a Windows VM working but I did discover the problem and\n> I'm working on a patch and will send it out once I have CI green.\n>\n> The problem is roughly that both the MSVC linker and MSYS linker are\n> both called link.exe. When compiling with Rust against MSVC, the MSVC\n> linker must be used, but the MSYS linker is first in PATH (because I\n> believe installing the Git for Windows SDK causes that to be the case),\n> causing build.rs to fail to compile.\n\nDidn't Ezekiel already tackle[*] this problem or am I misunderstanding?\n\n[*]: https://lore.kernel.org/git/CAPig+cSBEX5QGnzpBnVs_hKM2iUqcmA4-DzKDgkwpG9ZzWZ__w@mail.gmail.com/\n"},{"id":"534846","messageId":"aXvsb43Wq-YIYaVr@fruit.crustytoothpaste.net","threadId":"64873","inReplyTo":"CAPig+cStjN15WEKSN3b5VGLK-+N5pzj-dUDQ2rm15ne_9Q07FQ@mail.gmail.com","subject":"Re: What's cooking in git.git (Jan 2026, #09)","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2026-01-29T23:25:35Z","receivedAt":"2026-01-29T23:25:36Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2026-01-29 at 22:51:40, Eric Sunshine wrote:\n> On Thu, Jan 29, 2026 at 5:01 PM brian m. carlson\n> wrote:\n> > I did not get a Windows VM working but I did discover the problem and\n> > I'm working on a patch and will send it out once I have CI green.\n> >\n> > The problem is roughly that both the MSVC linker and MSYS linker are\n> > both called link.exe. When compiling with Rust against MSVC, the MSVC\n> > linker must be used, but the MSYS linker is first in PATH (because I\n> > believe installing the Git for Windows SDK causes that to be the case),\n> > causing build.rs to fail to compile.\n> \n> Didn't Ezekiel already tackle[*] this problem or am I misunderstanding?\n\nCI still fails when rebasing my branch on `master`, so it doesn't appear\nto have made it upstream quite yet. I'll resume working on this\ntomorrow at $DAYJOB and then add a patch to my series. I may steal the\napproach from Ezekiel's patch if it appears to work.\n-- \nbrian m. carlson (they/them)\nToronto, Ontario, CA\n"},{"id":"535388","messageId":"xmqq1pixek6j.fsf@gitster.g","threadId":"64873","inReplyTo":"aXk2FjTUMMThs5Kp@nand.local","subject":"Re: What's cooking in git.git (Jan 2026, #09)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-02-06T19:39:00Z","receivedAt":"2026-02-06T19:39:03Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Taylor Blau writes:\n\n> On Tue, Jan 27, 2026 at 09:42:00AM -0800, Junio C Hamano wrote:\n>> * ps/odb-for-each-object (2026-01-26) 16 commits\n>> - odb: drop unused `for_each_{loose,packed}_object()` functions\n>> - reachable: convert to use `odb_for_each_object()`\n>> - builtin/pack-objects: use `packfile_store_for_each_object()`\n>> - odb: introduce mtime fields for object info requests\n>> - treewide: drop uses of `for_each_{loose,packed}_object()`\n>> - treewide: enumerate promisor objects via `odb_for_each_object()`\n>> - builtin/fsck: refactor to use `odb_for_each_object()`\n>> - odb: introduce `odb_for_each_object()`\n>> - packfile: introduce function to iterate through objects\n>> - packfile: extract function to iterate through objects of a store\n>> - object-file: introduce function to iterate through objects\n>> - object-file: extract function to read object info from path\n>> - odb: fix flags parameter to be unsigned\n>> - odb: rename `FOR_EACH_OBJECT_*` flags\n>> - Merge branch 'ps/packfile-store-in-odb-source' into ps/odb-for-each-object\n>> - Merge branch 'ps/read-object-info-improvements' into ps/odb-for-each-object\n>>\n>> Revamp object enumeration API around odb.\n>>\n>> Will merge to 'next'?\n>> source: <20260126-pks-odb-for-each-object-v4-0-5a64a038c791@pks.im>\n>\n> I have some lingering questions about the mtime-related changes. I am\n> not opposed to the series in general, but I think some more time to\n> continue the discussion in that thread would be beneficial before\n> starting to merge it down.\n\nHas any further discussions took place outside the original thread\n\nhttps://lore.kernel.org/git/20260126-pks-odb-for-each-object-v4-0-5a64a038c791@pks.im/\n\nor are we pretty much done with this iteration and polish\nincrementally if necessary?\n\nThanks.\n\n"}]}