Subject: What's cooking in git.git (Apr 2026, #01)

From: Junio C Hamano <[email-masked]>
Date: Wed, 01 Apr 2026 16:42:10 -0700

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 and 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 they can be resubmitted 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.

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']

* bk/t5315-test-path-is-helpers (2026-03-19) 1 commit
  (merged to 'next' on 2026-03-24 at f7374e8e70)
 + t5315: use test_path_is_file for loose-object check

 Test clean-up.
 source: <[email-masked]>

* jc/macos-homebrew-wo-reg-enhanced (2026-03-23) 1 commit
  (merged to 'next' on 2026-03-26 at ce92a76711)
 + regexp: leave a pointer to resurrect workaround for Homebrew

 In case homebrew breaks REG_ENHANCED again, leave a in-code comment
 to suggest use of our replacement regex as a workaround.
 source: <[email-masked]>

* jk/diff-highlight-more (2026-03-22) 9 commits
  (merged to 'next' on 2026-03-24 at e7b555cbc5)
 + diff-highlight: fetch all config with one process
 + diff-highlight: allow module callers to pass in color config
 + diff-highlight: test color config
 + diff-highlight: use test_decode_color in tests
 + t: add matching negative attributes to test_decode_color
 + diff-highlight: check diff-highlight exit status in tests
 + diff-highlight: drop perl version dependency back to 5.8
 + diff-highlight: mention build instructions
 + Merge branch 'jk/diff-highlight-identical-pairs' into jk/diff-highlight-more

 Various updates to contrib/diff-highlight, including documentation
 updates, test improvements, and color configuration handling.
 source: <[email-masked]>

* jk/t0061-bat-test-update (2026-03-24) 1 commit
  (merged to 'next' on 2026-03-26 at ffae180124)
 + t0061: simplify .bat test

 A test to run a .bat file with whitespaces in the name with arguments
 with whitespaces in them was flaky in that sometimes it got killed
 before it produced expected side effects, which has been rewritten to
 make it more robust.
 source: <[email-masked]>

* kj/refspec-parsing-outside-repository (2026-03-23) 2 commits
  (merged to 'next' on 2026-03-26 at 0a8c60e8ae)
 + refspec: fix typo in comment
 + remote-curl: fall back to default hash outside repo

 "git ls-remote '+refs/tags/*:refs/tags/*' https://..." run outside a
 repository would dereference a NULL while trying to see if the given
 refspec is a single-object refspec, which has been corrected.
 source: <[email-masked]>

* mk/repo-help-strings (2026-03-25) 2 commits
  (merged to 'next' on 2026-03-26 at a4c755ddde)
 + repo: show subcommand-specific help text
 + repo: factor repo usage strings into shared macros

 "git repo info -h" and "git repo structure -h" limit their help output
 to the part that is specific to the subcommand.
 source: <20260323152937.257406-1-  [email-masked]>

* rs/use-strvec-pushv (2026-03-24) 2 commits
  (merged to 'next' on 2026-03-24 at 7c6487dcaf)
 + use strvec_pushv() to add another strvec
 + Merge branch 'ps/build-tweaks' into rs/use-strvec-pushv

 Code paths that loop over another array to push each element into a
 strvec have been rewritten to use strvec_pushv() instead.
 source: <[email-masked]>

* vp/http-rate-limit-retries (2026-03-17) 3 commits
  (merged to 'next' on 2026-03-24 at 9cb4ec5fad)
 + http: add support for HTTP 429 rate limit retries
 + strbuf_attach: fix call sites to pass correct alloc
 + strbuf: pass correct alloc to strbuf_attach() in strbuf_reencode()

 The HTTP transport learned to react to "429 Too Many Requests".
 cf. <[email-masked]>
 source: <[email-masked]>

--------------------------------------------------
[New Topics]

* jt/odb-transaction-write (2026-03-31) 7 commits
 - odb/transaction: make `write_object_stream()` pluggable
 - object-file: generalize packfile writes to use odb_write_stream
 - object-file: avoid fd seekback by checking object size upfront
 - object-file: remove flags from transaction packfile writes
 - odb: update `struct odb_write_stream` read() callback
 - odb/transaction: use pluggable `begin_transaction()`
 - odb: split `struct odb_transaction` into separate header

 ODB transaction interface is being reworked to explicitly handle
 object writes.

 Expecting a reroll.
 cf. <ac0irp8GJSrSD8GU@denethor>
 source: <[email-masked]>

* jd/cache-tree-trace-wo-the-repository (2026-03-31) 1 commit
 - cache-tree: use index state repository in trace2 calls

 Code cleanup.

 Will merge to 'next'?
 source: <[email-masked]>

* ps/reftable-portability (2026-03-31) 6 commits
 - reftable: introduce "reftable-system.h" header
 - reftable/system: add abstraction to mmap files
 - reftable/system: add abstraction to retrieve time in milliseconds
 - reftable/fsck: use REFTABLE_UNUSED instead of UNUSED
 - reftable/stack: don't call fsync(3p) unless provided
 - reftable/system: provide `REFTABLE_INLINE()` macro

 Update reftable library part with what is used in libgit2 to improve
 portability to different target codebases and platforms.

 Will merge to 'next'?
 source: <[email-masked]>

* jk/c23-const-preserving-fixes-more (2026-03-31) 12 commits
 - refs/files-backend: drop const to fix strchr() warning
 - http: drop const to fix strstr() warning
 - range-diff: drop const to fix strstr() warnings
 - pkt-line: make packet_reader.line non-const
 - skip_prefix(): check const match between in and out params
 - pseudo-merge: fix disk reads from find_pseudo_merge()
 - find_last_dir_sep(): convert inline function to macro
 - run-command: explicitly cast away constness when assigning to void
 - pager: explicitly cast away strchr() constness
 - transport-helper: drop const to fix strchr() warnings
 - http: add const to fix strchr() warnings
 - convert: add const to fix strchr() warnings

 Further work to adjust the codebase for C23 that changes functions
 like strchr() that discarded constness when they return a pointer into
 a const string to preserve constness.

 Will merge to 'next'?
 source: <[email-masked]>

* ps/odb-cleanup (2026-03-31) 7 commits
 - odb: drop unneeded headers and forward decls
 - odb: rename `odb_has_object()` flags
 - odb: use enum for `odb_write_object` flags
 - odb: rename `odb_write_object()` flags
 - treewide: use enum for `odb_for_each_object()` flags
 - CodingGuidelines: document our style for flags
 - Merge branch 'ps/odb-generic-object-name-handling' into ps/odb-cleanup
 (this branch uses ps/odb-generic-object-name-handling.)

 Various code clean-up around odb subsystem.

 Will merge to 'next'?
 source: <[email-masked]>

* ss/t7004-unhide-git-failures (2026-03-31) 1 commit
 - t7004: replace wc -l with modern test helpers

 Test clean-up.

 Will merge to 'next'.
 source: <[email-masked]>

* ng/add-files-to-cache-wo-rename (2026-04-01) 1 commit
 - read-cache: disable renames in add_files_to_cache

 add_files_to_cache() used diff_files() to detect only the paths that
 are different between the index and the working tree and add them,
 which does not need rename detection, which interfered with unnecessary
 conflicts.

 Will merge to 'next'?
 source: <[email-masked]>

--------------------------------------------------
[Cooking]

* sa/cat-file-batch-mailmap-switch (2026-03-31) 1 commit
 - cat-file: add mailmap subcommand to --batch-command

 "git cat-file --batch" learns an in-line command "mailmap"
 that lets the user toggle use of mailmap.

 Will merge to 'next'?
 source: <[email-masked]>

* sp/doc-gitignore-oowt (2026-03-28) 1 commit
  (merged to 'next' on 2026-03-31 at ab3e6e484e)
 + doc: gitignore: clarify pattern base for info/exclude and core.excludesFile

 Doc update.

 Will merge to 'master'.
 source: <[email-masked]>

* tb/incremental-midx-part-3.3 (2026-03-29) 16 commits
 - repack: allow `--write-midx=incremental` without `--geometric`
 - repack: introduce `--write-midx=incremental`
 - repack: implement incremental MIDX repacking
 - packfile: ensure `close_pack_revindex()` frees in-memory revindex
 - builtin/repack.c: convert `--write-midx` to an `OPT_CALLBACK`
 - repack-geometry: prepare for incremental MIDX repacking
 - repack-midx: extract `repack_fill_midx_stdin_packs()`
 - repack-midx: factor out `repack_prepare_midx_command()`
 - midx: expose `midx_layer_contains_pack()`
 - repack: track the ODB source via existing_packs
 - midx: support custom `--base` for incremental MIDX writes
 - midx: introduce `--checksum-only` for incremental MIDX writes
 - midx: use `strvec` for `keep_hashes`
 - strvec: introduce `strvec_init_alloc()`
 - midx: use `string_list` for retained MIDX files
 - midx-write: handle noop writes when converting incremental chains

 The repacking code has been refactored and compaction of MIDX layers
 have been implemented, and incremental strategy that does not require
 all-into-one repacking has been introduced.

 Expecting a reroll.
 cf. <[email-masked]>
 source: <[email-masked]>

* th/t6101-unhide-git-failures (2026-03-28) 1 commit
  (merged to 'next' on 2026-03-31 at 8867bcf2b4)
 + t6101: avoid suppressing git's exit code

 Test cleanup.

 Will merge to 'master'.
 source: <[email-masked]>

* za/t2000-modernise (2026-03-27) 1 commit
  (merged to 'next' on 2026-03-31 at 279c41a3e0)
 + t2000: modernise overall structure

 Test cleanup.

 Will merge to 'master'.
 source: <[email-masked]>

* jd/read-cache-trace-wo-the-repository (2026-03-30) 1 commit
  (merged to 'next' on 2026-04-01 at 7047e45a6d)
 + read-cache: use istate->repo for trace2 logging

 A handful of inappropriate uses of the_repository have been
 rewritten to use the right repository structure instance in the
 read-cache.c codepath.

 Will merge to 'master'.
 source: <[email-masked]>

* jd/unpack-trees-wo-the-repository (2026-03-31) 2 commits
 - unpack-trees: use repository from index instead of global
 - unpack-trees: use repository from index instead of global

 A handful of inappropriate uses of the_repository have been
 rewritten to use the right repository structure instance in the
 unpack-trees.c codepath.
 source: <[email-masked]>

* ps/receive-pack-updateinstead-in-worktree (2026-03-30) 3 commits
 - receive-pack: use worktree HEAD for updateInstead
 - t5516: clean up cloned and new-wt in denyCurrentBranch and worktrees test
 - t5516: test updateInstead with worktree and unborn bare HEAD

 The check in "receive-pack" to prevent a checked out branch from
 getting updated via updateInstead mechanism has been corrected.

 Will merge to 'next'.
 source: <[email-masked]>

* ps/setup-wo-the-repository (2026-03-30) 18 commits
 - setup: stop using `the_repository` in `init_db()`
 - setup: stop using `the_repository` in `create_reference_database()`
 - setup: stop using `the_repository` in `initialize_repository_version()`
 - setup: stop using `the_repository` in `check_repository_format()`
 - setup: stop using `the_repository` in `upgrade_repository_format()`
 - setup: stop using `the_repository` in `setup_git_directory()`
 - setup: stop using `the_repository` in `setup_git_directory_gently()`
 - setup: stop using `the_repository` in `setup_git_env()`
 - setup: stop using `the_repository` in `set_git_work_tree()`
 - setup: stop using `the_repository` in `setup_work_tree()`
 - setup: stop using `the_repository` in `enter_repo()`
 - setup: stop using `the_repository` in `verify_non_filename()`
 - setup: stop using `the_repository` in `verify_filename()`
 - setup: stop using `the_repository` in `path_inside_repo()`
 - setup: stop using `the_repository` in `prefix_path()`
 - setup: stop using `the_repository` in `is_inside_git_dir()`
 - setup: stop using `the_repository` in `is_inside_worktree()`
 - setup: replace use of `the_repository` in static functions

 Many uses of the_repository has been updated to use a more
 appropriate struct repository instance in setup.c codepath.

 Needs review.
 source: <[email-masked]>

* qb/doc-git-stash-push-optionality (2026-03-30) 1 commit
  (merged to 'next' on 2026-03-31 at 66ece1b5d6)
 + docs: fix "git stash [push]" documentation

 Doc update.

 Will merge to 'master'.
 source: <[email-masked]>

* kh/doc-trailers (2026-03-30) 2 commits
 - doc: interpret-trailers: explain key format
 - doc: interpret-trailers: stop fixating on RFC 822

 Documentation updates.

 Expecting a reroll.
 cf. <[email-masked]>
 source: <[email-masked]>

* tc/replay-ref (2026-03-25) 4 commits
 . replay: allow to specify a ref with option --ref
 . replay: use stuck form in documentation and help message
 . builtin/replay: mark options as not negatable
 . Merge branch 'sa/replay-revert' into tc/replay-ref
 (this branch uses sa/replay-revert.)

 The experimental `git replay` command learned the `--ref=<ref>` option
 to allow specifying which ref to update, overriding the default behavior.

 Seems to break CI.
 cf. <[email-masked]>
 source: <[email-masked]>

* jk/c23-const-preserving-fixes (2026-03-26) 5 commits
  (merged to 'next' on 2026-03-31 at c813b9b814)
 + config: store allocated string in non-const pointer
 + rev-parse: avoid writing to const string for parent marks
 + revision: avoid writing to const string for parent marks
 + rev-parse: simplify dotdot parsing
 + revision: make handle_dotdot() interface less confusing

 Adjust the codebase for C23 that changes functions like strchr()
 that discarded constness when they return a pointer into a const
 string to preserve constness.

 Will merge to 'master'.
 source: <[email-masked]>
 source: <[email-masked]>

* mf/format-patch-commit-list-format-doc (2026-03-27) 3 commits
  (merged to 'next' on 2026-03-31 at 8f775bd513)
 + format-patch: removing unconditional wrapping
 + docs: fix --commit-list-format related entries
 + Merge branch 'mf/format-patch-commit-list-format' into mf/format-patch-commit-list-format-doc
 (this branch uses mf/format-patch-commit-list-format and mf/format-patch-cover-letter-format.)

 Doc updates.

 Will merge to 'master'.
 source: <[email-masked]>

* th/t8003-unhide-git-failures (2026-03-28) 2 commits
  (merged to 'next' on 2026-03-30 at ad41378b07)
 + t8003: modernise style
 + t8003: avoid suppressing git's exit code

 Test clean-up.

 Will merge to 'master'.
 source: <[email-masked]>

* jt/fast-import-signed-modes (2026-03-26) 5 commits
 - fast-import: add 'abort-if-invalid' mode to '--signed-tags=<mode>'
 - fast-import: add 'sign-if-invalid' mode to '--signed-tags=<mode>'
 - fast-import: add 'strip-if-invalid' mode to '--signed-tags=<mode>'
 - fast-import: add 'abort-if-invalid' mode to '--signed-commits=<mode>'
 - fast-export: check for unsupported signing modes earlier

 Handling of signed commits and tags in fast-import has been made more
 configurable.

 Will merge to 'next'.
 source: <[email-masked]>

* ps/graph-lane-limit (2026-03-27) 3 commits
 - graph: add truncation mark to capped lanes
 - graph: add --graph-lane-limit option
 - graph: limit the graph width to a hard-coded max

 The graph output from commands like "git log --graph" can now be
 limited to a specified number of lanes, preventing overly wide output
 in repositories with many branches.

 Needs review.
 cf. <[email-masked]>
 source: <[email-masked]>

* cc/promisor-auto-config-url (2026-03-23) 16 commits
 - doc: promisor: improve acceptFromServer entry
 - promisor-remote: auto-configure unknown remotes
 - promisor-remote: trust known remotes matching acceptFromServerUrl
 - promisor-remote: introduce promisor.acceptFromServerUrl
 - t5710: use proper file:// URIs for absolute paths
 - promisor-remote: refactor should_accept_remote() control flow
 - promisor-remote: pass config entry to all_fields_match() directly
 - promisor-remote: add 'local_name' to 'struct promisor_info'
 - promisor-remote: remove the 'accepted' strvec
 - promisor-remote: keep accepted promisor_info structs alive
 - promisor-remote: refactor accept_from_server()
 - promisor-remote: refactor has_control_char()
 - promisor-remote: clarify that a remote is ignored
 - urlmatch: add url_is_valid_pattern() helper
 - urlmatch: change 'allow_globs' arg to bool
 - promisor-remote: try accepted remotes before others in get_direct()

 Promisor remote handling is enhanced to auto-configure remotes based
 on a URL whitelist.

 Expecting a reroll.
 cf. <CAP8UFD2vAK_khTkJMP4QBfhYA5iYVW5sfB3i-vnzhf71BvwQ=[email-masked]>
 source: <[email-masked]>

* ps/fsck-wo-the-repository (2026-03-23) 12 commits
  (merged to 'next' on 2026-04-01 at 6ab7607f2d)
 + builtin/fsck: stop using `the_repository` in error reporting
 + builtin/fsck: stop using `the_repository` when marking objects
 + builtin/fsck: stop using `the_repository` when checking packed objects
 + builtin/fsck: stop using `the_repository` with loose objects
 + builtin/fsck: stop using `the_repository` when checking reflogs
 + builtin/fsck: stop using `the_repository` when checking refs
 + builtin/fsck: stop using `the_repository` when snapshotting refs
 + builtin/fsck: fix trivial dependence on `the_repository`
 + fsck: drop USE_THE_REPOSITORY
 + fsck: store repository in fsck options
 + fsck: initialize fsck options via a function
 + fetch-pack: move fsck options into function scope

 Internals of "git fsck" have been refactored to not depend on the
 global `the_repository` variable.

 Will merge to 'master'.
 source: <[email-masked]>

* tb/stdin-packs-excluded-but-open (2026-03-27) 5 commits
  (merged to 'next' on 2026-03-31 at e8927aa861)
 + repack: mark non-MIDX packs above the split as excluded-open
 + pack-objects: support excluded-open packs with --stdin-packs
 + t7704: demonstrate failure with once-cruft objects above the geometric split
 + pack-objects: refactor `read_packs_list_from_stdin()` to use `strmap`
 + pack-objects: plug leak in `read_stdin_packs()`

 pack-objects's --stdin-packs=follow mode learns to handle
 excluded-but-open packs.

 Will merge to 'master'.
 source: <[email-masked]>

* yc/path-walk-fix-error-reporting (2026-03-20) 1 commit
  (merged to 'next' on 2026-04-01 at ddcff8b9c6)
 + path-walk: fix NULL pointer dereference in error message

 The value of a wrong pointer variable was referenced in an error
 message that reported that it shouldn't be NULL.

 Will merge to 'master'.
 source: <[email-masked]>

* jr/bisect-custom-terms-in-output (2026-03-20) 1 commit
 - bisect: use selected alternate terms in status output

 "git bisect" now uses the selected terms (e.g., old/new) more
 consistently in its output.

 Expecting a reroll?
 cf. <[email-masked]>
 source: <[email-masked]>

* jc/whitespace-incomplete-line (2026-03-17) 1 commit
  (merged to 'next' on 2026-04-01 at 10a4d95236)
 + apply: fix new-style empty context line triggering incomplete-line check

 Fix whitespace correction for new-style empty context lines.

 Will merge to 'master'.
 source: <[email-masked]>

* sp/add-patch-with-fewer-the-repository (2026-03-17) 1 commit
  (merged to 'next' on 2026-04-01 at b9edaddcff)
 + add-patch: use repository instance from add_i_state instead of the_repository

 Reduce dependency on `the_repository` in add-patch.c file.

 Will merge to 'master'.
 source: <[email-masked]>

* ds/backfill-revs (2026-03-26) 6 commits
  (merged to 'next' on 2026-03-27 at d4703fdd35)
 + t5620: test backfill's unknown argument handling
 + path-walk: support wildcard pathspecs for blob filtering
 + backfill: work with prefix pathspecs
 + backfill: accept revision arguments
 + t5620: prepare branched repo for revision tests
 + revision: include object-name.h

 `git backfill` learned to accept revision and pathspec arguments.

 Will merge to 'master'.
 source: <[email-masked]>

* ps/commit-graph-overflow-fix (2026-03-23) 1 commit
  (merged to 'next' on 2026-04-01 at c502054354)
 + commit-graph: fix writing generations with dates exceeding 34 bits

 Fix a regression in writing the commit-graph where commits with dates
 exceeding 34 bits (beyond year 2514) could cause an underflow and
 crash Git during the generation data overflow chunk writing.

 Will merge to 'master'.
 source: <[email-masked]>

* tc/replay-down-to-root (2026-03-24) 1 commit
  (merged to 'next' on 2026-03-31 at 47456fcc12)
 + replay: support replaying down from root commit

 git replay now supports replaying down to the root commit.

 Will merge to 'master'.
 source: <[email-masked]>

* ua/push-remote-group (2026-03-27) 3 commits
 - SQUASH??? - futureproof against the attack of the "main"
 - push: support pushing to a remote group
 - remote: move remote group resolution to remote.c

 "git push" learned to take a "remote group" name to push to, which
 causes pushes to multiple places, just like "git fetch" would do.

 Expecting a reroll.
 cf. <[email-masked]>
 cf. <[email-masked]>
 source: <[email-masked]>

* ps/odb-generic-object-name-handling (2026-03-20) 16 commits
  (merged to 'next' on 2026-03-31 at c14d7bdd1e)
 + odb: introduce generic `odb_find_abbrev_len()`
 + object-file: move logic to compute packed abbreviation length
 + object-name: move logic to compute loose abbreviation length
 + object-name: simplify computing common prefixes
 + object-name: abbreviate loose object names without `disambiguate_state`
 + object-name: merge `update_candidates()` and `match_prefix()`
 + object-name: backend-generic `get_short_oid()`
 + object-name: backend-generic `repo_collect_ambiguous()`
 + object-name: extract function to parse object ID prefixes
 + object-name: move logic to iterate through packed prefixed objects
 + object-name: move logic to iterate through loose prefixed objects
 + odb: introduce `struct odb_for_each_object_options`
 + oidtree: extend iteration to allow for arbitrary return codes
 + oidtree: modernize the code a bit
 + Merge branch 'ps/object-counting' into ps/odb-generic-object-name-handling
 + object-file: fix sparse 'plain integer as NULL pointer' error
 (this branch is used by ps/odb-cleanup.)

 Object name handling (disambiguation and abbreviation) has been
 refactored to be backend-generic, moving logic into the respective
 object database backends.

 Will merge to 'master'.
 cf. <[email-masked]>
 source: <[email-masked]>

* aa/reap-transport-child-processes (2026-03-12) 1 commit
  (merged to 'next' on 2026-03-31 at fb77f8ba9e)
 + transport-helper, connect: use clean_on_exit to reap children on abnormal exit

 A few code paths that spawned child processes for network
 connection weren't wait(2)ing for their children and letting "init"
 reap them instead; they have been tightened.

 Will merge to 'master'.
 cf. <[email-masked]>
 source: <[email-masked]>

* hn/git-checkout-m-with-stash (2026-03-17) 4 commits
 - checkout: -m (--merge) uses autostash when switching branches
 - sequencer: teach autostash apply to take optional conflict marker labels
 - sequencer: allow create_autostash to run silently
 - stash: add --ours-label, --theirs-label, --base-label for apply

 "git checkout -m another-branch" was invented to deal with local
 changes to paths that are different between the current and the new
 branch, but it gave only one chance to resolve conflicts.  The command
 was taught to create a stash to save the local changes.

 Needs review.
 source: <[email-masked]>

* kh/name-rev-custom-format (2026-03-20) 2 commits
 - name-rev: learn --format=<pretty>
 - name-rev: wrap both blocks in braces

 "git name-rev" learned to use custom format instead of the object
 name in an extended SHA-1 expression form.

 Comments?
 source: <[email-masked]>

* pw/worktree-reduce-the-repository (2026-03-26) 3 commits
  (merged to 'next' on 2026-03-30 at f967ececef)
 + worktree: reject NULL worktree in get_worktree_git_dir()
 + worktree add: stop reading ".git/HEAD"
 + worktree: remove "the_repository" from is_current_worktree()

 Reduce the reference to the_repository in the worktree subsystem.

 Will merge to 'master'.
 source: <[email-masked]>

* mf/format-patch-commit-list-format (2026-03-23) 9 commits
  (merged to 'next' on 2026-03-24 at 0f5b6702eb)
 + format-patch: --commit-list-format without prefix
 + format-patch: add preset for --commit-list-format
 + format-patch: wrap generate_commit_list_cover()
 + format.commitListFormat: strip meaning from empty
 + docs/pretty-formats: add %(count) and %(total)
 + format-patch: rename --cover-letter-format option
 + format-patch: refactor generate_commit_list_cover
 + pretty.c: better die message %(count) and %(total)
 + Merge branch 'mf/format-patch-cover-letter-format' into mf/format-patch-commit-list-format
 (this branch is used by mf/format-patch-commit-list-format-doc; uses mf/format-patch-cover-letter-format.)

 Improve the recently introduced `git format-patch
 --commit-list-format` (formerly `--cover-letter-format`) option,
 including a new "modern" preset and better CLI ergonomics.

 Waiting for the follow-on topic.
 source: <[email-masked]>

* js/parseopt-subcommand-autocorrection (2026-03-16) 10 commits
 - doc: document autocorrect API
 - parseopt: add tests for subcommand autocorrection
 - parseopt: enable subcommand autocorrection for git-remote and git-notes
 - parseopt: autocorrect mistyped subcommands
 - autocorrect: provide config resolution API
 - autocorrect: rename AUTOCORRECT_SHOW to AUTOCORRECT_HINT
 - autocorrect: use mode and delay instead of magic numbers
 - help: move tty check for autocorrection to autocorrect.c
 - help: make autocorrect handling reusable
 - parseopt: extract subcommand handling from parse_options_step()

 The parse-options library learned to auto-correct misspelled
 subcommand names.

 Expecting review responses.
 cf. <[email-masked]>
 source: <[email-masked]>

* mm/line-log-use-standard-diff-output (2026-03-16) 4 commits
 - doc: note that -L supports patch formatting and pickaxe options
 - t4211: add tests for -L with standard diff options
 - line-log: route -L output through the standard diff pipeline
 - line-log: fix crash when combined with pickaxe options

 The way the "git log -L<range>:<file>" feature is bolted onto the
 log/diff machinery is being reworked a bit to make the feature
 compatible with more diff options, like -S/G.

 Will merge to 'next'.
 cf. <[email-masked]>
 source: <[email-masked]>

* ar/config-hook-cleanups (2026-03-25) 13 commits
  (merged to 'next' on 2026-03-30 at c128948b16)
 + hook: reject unknown hook names in git-hook(1)
 + hook: show disabled hooks in "git hook list"
 + hook: show config scope in git hook list
 + hook: introduce hook_config_cache_entry for per-hook data
 + t1800: add test to verify hook execution ordering
 + hook: make consistent use of friendly-name in docs
 + hook: replace hook_list_clear() -> string_list_clear_func()
 + hook: detect & emit two more bugs
 + hook: rename cb_data_free/alloc -> hook_data_free/alloc
 + hook: fix minor style issues
 + builtin/receive-pack: properly init receive_hook strbuf
 + hook: move unsorted_string_list_remove() to string-list.[ch]
 + Merge branch 'ar/config-hooks' into ar/config-hook-cleanups
 (this branch is used by ar/parallel-hooks.)

 Code clean-up around the recent "hooks defined in config" topic.

 Will merge to 'master'.
 source: <[email-masked]>

* ab/clone-default-object-filter (2026-03-14) 1 commit
 - clone: add clone.<url>.defaultObjectFilter config

 "git clone" learns to pay attention to "clone.<url>.defaultObjectFilter"
 configuration and behave as if the "--filter=<filter-spec>" option
 was given on the command line.

 Expecting review responses.
 cf. <[email-masked]>
 source: <[email-masked]>

* jc/neuter-sideband-fixup (2026-03-05) 6 commits
  (merged to 'next' on 2026-03-13 at 5a4098b0cd)
 + sideband: drop 'default' configuration
 + 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
 (this branch is used by jc/neuter-sideband-post-3.0.)

 Try to resurrect and reboot a stalled "avoid sending risky escape
 sequences taken from sideband to the terminal" topic by Dscho.  The
 plan is to keep it in 'next' long enough to see if anybody screams
 with the "everything dropped except for ANSI color escape sequences"
 default.

 Will keep in 'next' a bit longer than usual.
 source: <[email-masked]>

* jc/neuter-sideband-post-3.0 (2026-03-05) 2 commits
 - sideband: delay sanitizing by default to Git v3.0
 - Merge branch 'jc/neuter-sideband-fixup' into jc/neuter-sideband-post-3.0
 (this branch uses jc/neuter-sideband-fixup.)

 The final step, split from earlier attempt by Dscho, to loosen the
 sideband restriction for now and tighten later at Git v3.0 boundary.

 On hold, until jc/neuter-sideband-fixup cooks long enough in 'next'.
 (this branch uses jc/neuter-sideband-fixup.)
 source: <[email-masked]>

* cs/subtree-split-recursion (2026-03-05) 3 commits
 - contrib/subtree: reduce recursion during split
 - contrib/subtree: functionalize split traversal
 - contrib/subtree: reduce function side-effects

 When processing large history graphs on Debian or Ubuntu, "git
 subtree" can die with a "recursion depth reached" error.

 Comments?
 source: <[email-masked]>

* pt/promisor-lazy-fetch-no-recurse (2026-03-11) 1 commit
 - promisor-remote: prevent lazy-fetch recursion in child fetch

 The mechanism to avoid recursive lazy-fetch from promisor remotes
 was not propagated properly to child "git fetch" processes, which
 has been corrected.

 Comments?
 source: <[email-masked]>

* mf/format-patch-cover-letter-format (2026-03-06) 5 commits
  (merged to 'next' on 2026-03-09 at e872adca7b)
 + docs: add usage for the cover-letter fmt feature
 + format-patch: add commitListFormat config
 + format-patch: add ability to use alt cover format
 + format-patch: move cover letter summary generation
 + pretty.c: add %(count) and %(total) placeholders
 (this branch is used by mf/format-patch-commit-list-format and mf/format-patch-commit-list-format-doc.)

 "git format-patch --cover-letter" learns to use a simpler format
 instead of the traditional shortlog format to list its commits with
 a new --cover-letter-format option and format.commitListFormat
 configuration variable.

 Waiting for the follow-on topic.
 source: <[email-masked]>

* pt/fsmonitor-linux (2026-03-30) 13 commits
 - fsmonitor: fix split-index bitmap bounds in tweak_fsmonitor()
 - fsmonitor: convert shown khash to strset in do_handle_client
 - fsmonitor: add tests for Linux
 - fsmonitor: add timeout to daemon stop command
 - fsmonitor: close inherited file descriptors and detach in daemon
 - run-command: add close_fd_above_stderr option
 - fsmonitor: implement filesystem change listener for Linux
 - fsmonitor: rename fsm-settings-darwin.c to fsm-settings-unix.c
 - fsmonitor: rename fsm-ipc-darwin.c to fsm-ipc-unix.c
 - fsmonitor: use pthread_cond_timedwait for cookie wait
 - compat/win32: add pthread_cond_timedwait
 - fsmonitor: fix hashmap memory leak in fsmonitor_run_daemon
 - fsmonitor: fix khash memory leak in do_handle_client

 The fsmonitor daemon has been implemented for Linux.

 Needs review.
 source: <[email-masked]>

* sa/replay-revert (2026-03-25) 2 commits
  (merged to 'next' on 2026-03-30 at ef4896a676)
 + replay: add --revert mode to reverse commit changes
 + sequencer: extract revert message formatting into shared function
 (this branch is used by tc/replay-ref.)

 "git replay" (experimental) learns, in addition to "pick" and
 "replay", a new operating mode "revert".

 Will merge to 'master'.
 source: <[email-masked]>

* ar/parallel-hooks (2026-03-26) 13 commits
 - hook: allow hook.jobs=-1 to use all available CPU cores
 - hook: add hook.<event>.enabled switch
 - hook: move is_known_hook() to hook.c for wider use
 - hook: warn when hook.<friendly-name>.jobs is set
 - hook: add per-event jobs config
 - hook: add -j/--jobs option to git hook run
 - hook: mark non-parallelizable hooks
 - hook: allow pre-push parallel execution
 - hook: allow parallel hook execution
 - hook: parse the hook.jobs config
 - config: add a repo_config_get_uint() helper
 - repository: fix repo_init() memleak due to missing _clear()
 - Merge branch 'ar/config-hook-cleanups' into ar/parallel-hooks
 (this branch uses ar/config-hook-cleanups.)

 Needs review.
 source: <[email-masked]>

* en/xdiff-cleanup-3 (2026-03-30) 6 commits
 - xdiff/xdl_cleanup_records: simplify INVESTIGATE handling for clarity
 - xdiff/xdl_cleanup_records: make setting action easier to follow
 - xdiff/xdl_cleanup_records: make limits more clear
 - xdiff/xdl_cleanup_records: use unambiguous types
 - xdiff: use unambiguous types in xdl_bogo_sqrt()
 - xdiff/xdl_cleanup_records: delete local recs pointer

 Preparation of the xdiff/ codebase to work with Rust

 Expecting a (hopefully small and final) reroll?
 cf. <[email-masked]>
 cf. <[email-masked]>
 cf. <[email-masked]>
 source: <[email-masked]>

--------------------------------------------------
[Discarded]

* bc/rev-parse-parseopt-help-exit-code (2026-03-16) 1 commit
 . rev-parse: have --parseopt callers exit 0 on --help

 `rev-parse --parseopt` now includes "exit 0" in its output when the
 user asks for help, ensuring that scripts using the recommended `eval`
 pattern exit successfully.

 Need to step back and rethink how exit code should look like.
 cf. <[email-masked]>
 source: <[email-masked]>

* js/macos-homebrew-forgets-reg-enhanced (2026-03-20) 1 commit
 . osx-clang: work around Homebrew's clang lacking REG_ENHANCED

 The build on macOS with Clang is fixed to work around a Homebrew change
 that exposed an issue with missing REG_ENHANCED.

 No longer needed?
 cf. <[email-masked]>
 cf. <[email-masked]>
 cf. <[email-masked]>
 source: <[email-masked]>