{"thread":{"id":"65348","subject":"What's cooking in git.git (Mar 2026, #10)","startedAt":"2026-03-25T04:20:43Z","lastAt":"2026-03-26T19:44:35Z","messageCount":8,"participants":["Junio C Hamano","Jeff King","Shreyansh Paliwal","Kristoffer Haugsbakk"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"539891","messageId":"xmqqldfgy1ye.fsf@gitster.g","threadId":"65348","inReplyTo":null,"subject":"What's cooking in git.git (Mar 2026, #10)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-03-25T04:20:41Z","receivedAt":"2026-03-25T04:20:43Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":null},"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 is a 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 a URL\nto a message that raises issues but they are by no means exhaustive.\nA topic without enough support may be discarded after a long period\nof no activity (of course they can be resubmitted 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\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[Graduated to 'master']\n\n* dd/cocci-do-not-pass-strbuf-by-value (2026-03-15) 3 commits\n (merged to 'next' on 2026-03-18 at a2ffed1127)\n + stash: do not pass strbuf by value\n + coccinelle: detect struct strbuf passed by value\n + Merge branch 'dd/list-objects-filter-options-wo-strbuf-split' into dd/cocci-do-not-pass-strbuf-by-value\n\n Add a coccinelle rule to break the build when \"struct strbuf\" gets\n passed by value.\n source: <20260315094445.19849-1-deveshigurgaon@gmail.com>\n\n\n* gj/user-manual-fix-grep-example (2026-03-16) 1 commit\n (merged to 'next' on 2026-03-17 at dbf9137a9d)\n + doc: fix git grep args order in Quick Reference\n\n Fix an example in the user-manual.\n source: \n\n\n* jk/transport-color-leakfix (2026-03-14) 1 commit\n (merged to 'next' on 2026-03-17 at c2d7c74d11)\n + transport: plug leaks in transport_color_config()\n\n Leakfix.\n source: <20260314160814.GA918806@coredump.intra.peff.net>\n\n\n* jt/fast-import-sign-again (2026-03-12) 3 commits\n (merged to 'next' on 2026-03-17 at e04808d5f2)\n + fast-import: add mode to sign commits with invalid signatures\n + gpg-interface: allow sign_buffer() to use default signing key\n + commit: remove unused forward declaration\n\n \"git fast-import\" learned to optionally replace signature on\n commits whose signatures get invalidated due to replaying by\n signing afresh.\n source: <20260313013938.2742124-1-jltobler@gmail.com>\n\n\n* mf/t0008-cleanup (2026-03-15) 1 commit\n (merged to 'next' on 2026-03-17 at 2bb0e51243)\n + t0008: improve test cleanup to fix failing test\n\n Test clean-up.\n source: <20260316011544.13825-1-mroik@delayed.space>\n\n\n* pb/t4200-test-path-is-helpers (2026-03-16) 1 commit\n (merged to 'next' on 2026-03-17 at a78771f93e)\n + t4200: convert test -[df] checks to test_path_* helpers\n\n Test clean-up.\n source: <20260316172457.38242-1-prashantjee2025@gmail.com>\n\n\n* ps/clar-wo-path-max (2026-03-16) 1 commit\n (merged to 'next' on 2026-03-17 at 1d2f28a677)\n + clar: update to fix compilation on platforms without PATH_MAX\n\n Clar (unit testing framework) update from the upstream.\n source: <20260316-b4-pks-clar-without-path-max-v1-1-40b4bc91fdc0@pks.im>\n\n\n* ps/history-split (2026-03-02) 8 commits\n (merged to 'next' on 2026-03-17 at 456723f018)\n + builtin/history: implement \"split\" subcommand\n + builtin/history: split out extended function to create commits\n + cache-tree: allow writing in-memory index as tree\n + add-patch: allow disabling editing of hunks\n + add-patch: add support for in-memory index patching\n + add-patch: remove dependency on \"add-interactive\" subsystem\n + add-patch: split out `struct interactive_options`\n + add-patch: split out header from \"add-interactive.h\"\n\n \"git history\" learned the \"split\" subcommand.\n source: <20260302-pks-history-split-v1-0-444fc987a324@pks.im>\n\n\n* ps/upload-pack-buffer-more-writes (2026-03-12) 10 commits\n (merged to 'next' on 2026-03-18 at 138ad42ac5)\n + builtin/pack-objects: reduce lock contention when writing packfile data\n + csum-file: drop `hashfd_throughput()`\n + csum-file: introduce `hashfd_ext()`\n + sideband: use writev(3p) to send pktlines\n + wrapper: introduce writev(3p) wrappers\n + compat/posix: introduce writev(3p) wrapper\n + upload-pack: reduce lock contention when writing packfile data\n + upload-pack: prefer flushing data over sending keepalive\n + upload-pack: adapt keepalives based on buffering\n + upload-pack: fix debug statement when flushing packfile data\n\n Reduce system overhead \"git upload-pack\" spends on relaying \"git\n pack-objects\" output to the \"git fetch\" running on the other end of\n the connection.\n source: <20260313-pks-upload-pack-write-contention-v4-0-7a9668061f7f@pks.im>\n\n\n* rj/pack-refs-tests-path-is-helpers (2026-03-15) 1 commit\n (merged to 'next' on 2026-03-17 at 56374095e3)\n + t/pack-refs-tests: use test_path_is_missing\n\n Test updates.\n source: <20260315081032.497-1-riteshjd75@gmail.com>\n\n\n* ss/t0410-delete-object-cleanup (2026-03-12) 1 commit\n (merged to 'next' on 2026-03-17 at a8d41f4c1f)\n + t0410: modernize delete_object helper\n\n Test clean-up.\n source: <20260313053159.36492-1-r.siddharth.shrimali@gmail.com>\n\n\n* ty/doc-diff-u-wo-number (2026-03-10) 1 commit\n (merged to 'next' on 2026-03-18 at 8a410154ff)\n + diff: document -U without as using default context\n\n \"git diff -U\" was too lenient in its command line parsing and\n took an empty string as a valid .\n source: <20260310095017.131957-1-cat@malon.dev>\n\n\n* yc/histogram-hunk-shift-fix (2026-03-02) 1 commit\n (merged to 'next' on 2026-03-18 at 5e49edc821)\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 source: \n\n--------------------------------------------------\n[New Topics]\n\n* jt/fast-import-signed-modes (2026-03-24) 4 commits\n - fast-import: add 'abort-if-invalid' mode to '--signed-tags='\n - fast-import: add 'sign-if-invalid' mode to '--signed-tags='\n - fast-import: add 'strip-if-invalid' mode to '--signed-tags='\n - fast-import: add 'abort-if-invalid' mode to '--signed-commits='\n\n Handling of signed commits and tags in fast-import has been made more\n configurable.\n source: <20260324215513.764739-1-jltobler@gmail.com>\n\n--------------------------------------------------\n[Cooking]\n\n* ps/graph-lane-limit (2026-03-23) 3 commits\n - graph: add documentation and tests about --graph-lane-limit\n - graph: truncate graph visual output\n - graph: add --graph-lane-limit option\n\n The graph output from commands like \"git log --graph\" can now be\n limited to a specified number of lanes, preventing overly wide output\n in repositories with many branches.\n\n Needs review.\n source: <20260323215935.74486-1-pabloosabaterr@gmail.com>\n\n\n* rs/use-strvec-pushv (2026-03-24) 2 commits\n (merged to 'next' on 2026-03-24 at 7c6487dcaf)\n + use strvec_pushv() to add another strvec\n + Merge branch 'ps/build-tweaks' into rs/use-strvec-pushv\n (this branch uses ps/build-tweaks.)\n\n Code paths that loop over another array to push each element into a\n strvec have been rewritten to use strvec_pushv() instead.\n\n Will merge to 'master'.\n source: <084f3b43-91ac-4553-8305-03944e97eaa6@web.de>\n\n\n* cc/promisor-auto-config-url (2026-03-23) 16 commits\n - doc: promisor: improve acceptFromServer entry\n - promisor-remote: auto-configure unknown remotes\n - promisor-remote: trust known remotes matching acceptFromServerUrl\n - promisor-remote: introduce promisor.acceptFromServerUrl\n - t5710: use proper file:// URIs for absolute paths\n - promisor-remote: refactor should_accept_remote() control flow\n - promisor-remote: pass config entry to all_fields_match() directly\n - promisor-remote: add 'local_name' to 'struct promisor_info'\n - promisor-remote: remove the 'accepted' strvec\n - promisor-remote: keep accepted promisor_info structs alive\n - promisor-remote: refactor accept_from_server()\n - promisor-remote: refactor has_control_char()\n - promisor-remote: clarify that a remote is ignored\n - urlmatch: add url_is_valid_pattern() helper\n - urlmatch: change 'allow_globs' arg to bool\n - promisor-remote: try accepted remotes before others in get_direct()\n\n Promisor remote handling is enhanced to auto-configure remotes based\n on a URL whitelist.\n\n Needs review.\n source: <20260323080520.887550-1-christian.couder@gmail.com>\n\n\n* kj/refspec-parsing-outside-repository (2026-03-23) 2 commits\n - refspec: fix typo in comment\n - remote-curl: fall back to default hash outside repo\n\n \"git ls-remote '+refs/tags/*:refs/tags/*' https://...\" run outside a\n repository would dereference a NULL while trying to see if the given\n refspec is a single-object refspec, which has been corrected.\n\n Will merge to 'next'?\n source: <20260324015734.18470-1-jayatheerthkulkarni2005@gmail.com>\n\n\n* jk/diff-highlight-identical-pairs (2026-03-17) 1 commit\n (merged to 'next' on 2026-03-20 at a8aa5bd14e)\n + contrib/diff-highlight: do not highlight identical pairs\n (this branch is used by jk/diff-highlight-more.)\n\n The handling of the incomplete lines at the end by \"git\n diff-highlight\" has been fixed.\n\n Will merge to 'master'.\n source: <20260317230223.GA716496@coredump.intra.peff.net>\n\n\n* jk/diff-highlight-more (2026-03-22) 9 commits\n (merged to 'next' on 2026-03-24 at e7b555cbc5)\n + diff-highlight: fetch all config with one process\n + diff-highlight: allow module callers to pass in color config\n + diff-highlight: test color config\n + diff-highlight: use test_decode_color in tests\n + t: add matching negative attributes to test_decode_color\n + diff-highlight: check diff-highlight exit status in tests\n + diff-highlight: drop perl version dependency back to 5.8\n + diff-highlight: mention build instructions\n + Merge branch 'jk/diff-highlight-identical-pairs' into jk/diff-highlight-more\n (this branch uses jk/diff-highlight-identical-pairs.)\n\n Various updates to contrib/diff-highlight, including documentation\n updates, test improvements, and color configuration handling.\n\n Will merge to 'master'.\n source: <20260323060139.GA10215@coredump.intra.peff.net>\n\n\n* ps/fsck-wo-the-repository (2026-03-23) 12 commits\n - builtin/fsck: stop using `the_repository` in error reporting\n - builtin/fsck: stop using `the_repository` when marking objects\n - builtin/fsck: stop using `the_repository` when checking packed objects\n - builtin/fsck: stop using `the_repository` with loose objects\n - builtin/fsck: stop using `the_repository` when checking reflogs\n - builtin/fsck: stop using `the_repository` when checking refs\n - builtin/fsck: stop using `the_repository` when snapshotting refs\n - builtin/fsck: fix trivial dependence on `the_repository`\n - fsck: drop USE_THE_REPOSITORY\n - fsck: store repository in fsck options\n - fsck: initialize fsck options via a function\n - fetch-pack: move fsck options into function scope\n\n Internals of \"git fsck\" have been refactored to not depend on the\n global `the_repository` variable.\n\n Needs review.\n source: <20260323-b4-pks-fsck-without-the-repository-v2-0-e8dc79bca651@pks.im>\n\n\n* tb/stdin-packs-excluded-but-open (2026-03-19) 5 commits\n - repack: mark non-MIDX packs above the split as excluded-open\n - pack-objects: support excluded-open packs with --stdin-packs\n - t7704: demonstrate failure with once-cruft objects above the geometric split\n - pack-objects: refactor `read_packs_list_from_stdin()` to use `strmap`\n - pack-objects: plug leak in `read_stdin_packs()`\n\n pack-objects's --stdin-packs=follow mode learns to handle\n excluded-but-open packs.\n\n Comments?\n source: \n\n\n* yc/path-walk-fix-error-reporting (2026-03-20) 1 commit\n - path-walk: fix NULL pointer dereference in error message\n\n The value of a wrong pointer variable was referenced in an error\n message that reported that it shouldn't be NULL.\n\n Reproduction being discussed.\n cf. <994f92e9-3576-455a-a142-0fefc559131c@gmail.com>\n source: <20260320114823.3151961-1-ysinghcin@gmail.com>\n\n\n* jr/bisect-custom-terms-in-output (2026-03-20) 1 commit\n - bisect: use selected alternate terms in status output\n\n \"git bisect\" now uses the selected terms (e.g., old/new) more\n consistently in its output.\n\n Expecting a reroll?\n cf. \n source: <20260320-bisect-terms-v1-1-c30c9540542a@schlaraffenlan.de>\n\n\n* jc/whitespace-incomplete-line (2026-03-17) 1 commit\n - apply: fix new-style empty context line triggering incomplete-line check\n\n Fix whitespace correction for new-style empty context lines.\n\n Needs review.\n source: \n\n\n* sp/add-patch-with-fewer-the-repository (2026-03-17) 1 commit\n - add-patch: use repository instance from add_i_state instead of the_repository\n\n Reduce dependency on `the_repository` in add-patch.c file.\n\n Needs review.\n source: <20260317155230.619378-1-shreyanshpaliwalcmsmn@gmail.com>\n\n\n* ds/backfill-revs (2026-03-23) 6 commits\n - t5620: test backfill's unknown argument handling\n - path-walk: support wildcard pathspecs for blob filtering\n - backfill: work with prefix pathspecs\n - backfill: accept revision arguments\n - t5620: prepare branched repo for revision tests\n - revision: include object-name.h\n\n `git backfill` learned to accept revision and pathspec arguments.\n\n Comments?\n source: \n\n\n* jw/t2203-status-pipe-fix (2026-03-16) 1 commit\n (merged to 'next' on 2026-03-23 at 521c6eb44b)\n + t2203: avoid suppressing git status exit code\n\n Test clean-up.\n\n Will merge to 'master'.\n source: <20260317011544.65952-1-jerrywang183@yahoo.com>\n\n\n* ps/commit-graph-overflow-fix (2026-03-23) 1 commit\n - commit-graph: fix writing generations with dates exceeding 34 bits\n\n Fix a regression in writing the commit-graph where commits with dates\n exceeding 34 bits (beyond year 2514) could cause an underflow and\n crash Git during the generation data overflow chunk writing.\n\n Waiting for review response.\n cf. \n source: <20260324-pks-commit-graph-overflow-v2-1-843568cf8780@pks.im>\n\n\n* tc/replay-down-to-root (2026-03-24) 1 commit\n - replay: support replaying down from root commit\n\n git replay now supports replaying down to the root commit.\n\n Will merge to 'next'?\n source: <20260324-toon-replay-down-to-root-v2-1-34e723489f6e@iotcl.com>\n\n\n* mr/merge-file-object-id-worktree-fix (2026-03-10) 1 commit\n (merged to 'next' on 2026-03-20 at 68e1ee2045)\n + merge-file: fix BUG when --object-id is used in a worktree\n\n merge-file --object-id used to trigger a BUG when run in a linked\n worktree, which has been fixed.\n\n Will merge to 'master'.\n source: \n\n\n* rs/prio-queue-to-commit-stack (2026-03-17) 1 commit\n (merged to 'next' on 2026-03-20 at 265cb7b28c)\n + use commit_stack instead of prio_queue in LIFO mode\n\n Uses of prio_queue as a LIFO stack of commits have been written\n with commit_stack.\n\n Will merge to 'master'.\n source: <05fc946f-6670-46e9-a058-231ee464029d@web.de>\n\n\n* jw/object-name-bitset-to-enum (2026-03-18) 1 commit\n (merged to 'next' on 2026-03-23 at 881af371ef)\n + object-name: turn INTERPRET_BRANCH_* constants into enum values\n\n The unsigned integer that is used as an bitset to specify the kind\n of branches interpret_branch_name() function has been changed to\n use a dedicated enum type.\n\n Will merge to 'master'.\n source: <20260318190942.22595-1-jerrywang183@yahoo.com>\n\n\n* ai/t2107-test-path-is-helpers (2026-03-18) 1 commit\n (merged to 'next' on 2026-03-23 at 56d10e5f76)\n + t2107: modernize path existence check\n\n Test cleanup.\n\n Will merge to 'master'.\n source: \n\n\n* gi/doc-boolean-config-typofix (2026-03-18) 1 commit\n (merged to 'next' on 2026-03-20 at 8810624798)\n + doc: add missing space on git-config page\n\n Doc typofix.\n\n Will merge to 'master'.\n source: <20260318210020.759128-1-gabl@gabl.ink>\n\n\n* ua/push-remote-group (2026-03-18) 2 commits\n - push: support pushing to a remote group\n - remote: move remote group resolution to remote.c\n\n \"git push\" learned to take a \"remote group\" name to push to, which\n causes pushes to multiple places, just like \"git fetch\" would do.\n\n Expecting a (hopefully small and final) reroll?\n cf. <20260318204028.1010487-1-usmanakinyemi202@gmail.com>\n source: <20260318204028.1010487-1-usmanakinyemi202@gmail.com>\n\n\n* jc/rerere-modern-strbuf-handling (2026-03-19) 2 commits\n (merged to 'next' on 2026-03-21 at 919b766afc)\n + cocci: strbuf.buf is never NULL\n + rerere: update to modern representation of empty strbufs\n\n Code clean-up overdue by 19 years.\n\n Will merge to 'master'.\n source: \n source: \n\n\n* ps/odb-generic-object-name-handling (2026-03-20) 16 commits\n - odb: introduce generic `odb_find_abbrev_len()`\n - object-file: move logic to compute packed abbreviation length\n - object-name: move logic to compute loose abbreviation length\n - object-name: simplify computing common prefixes\n - object-name: abbreviate loose object names without `disambiguate_state`\n - object-name: merge `update_candidates()` and `match_prefix()`\n - object-name: backend-generic `get_short_oid()`\n - object-name: backend-generic `repo_collect_ambiguous()`\n - object-name: extract function to parse object ID prefixes\n - object-name: move logic to iterate through packed prefixed objects\n - object-name: move logic to iterate through loose prefixed objects\n - odb: introduce `struct odb_for_each_object_options`\n - oidtree: extend iteration to allow for arbitrary return codes\n - oidtree: modernize the code a bit\n - Merge branch 'ps/object-counting' into ps/odb-generic-object-name-handling\n - object-file: fix sparse 'plain integer as NULL pointer' error\n (this branch uses ps/object-counting.)\n\n Object name handling (disambiguation and abbreviation) has been\n refactored to be backend-generic, moving logic into the respective\n object database backends.\n\n Comments?\n source: <20260320-b4-pks-odb-source-abbrev-v2-0-fe65dcd8c735@pks.im>\n\n\n* rs/ahead-behind-cleanup-optimization (2026-03-19) 1 commit\n (merged to 'next' on 2026-03-21 at 5d8b4fa265)\n + commit-reach: simplify cleanup of remaining bitmaps in ahead_behind ()\n\n The cleanup of remaining bitmaps in \"ahead_behind()\" has been\n simplified.\n\n Will merge to 'master'.\n source: <21adf042-2bd1-4022-8822-9ed4985122a4@web.de>\n\n\n* bk/t5315-test-path-is-helpers (2026-03-19) 1 commit\n (merged to 'next' on 2026-03-24 at f7374e8e70)\n + t5315: use test_path_is_file for loose-object check\n\n Test clean-up.\n\n Will merge to 'master'.\n source: <20260319180803.164335-1-elkhatabibilal@gmail.com>\n\n\n* rs/split-index-the-repo-fix (2026-03-19) 1 commit\n (merged to 'next' on 2026-03-21 at d66850b2ce)\n + split-index: stop using the_repository and the_hash_algo\n\n split-index.c has been updated to not use the global the_repository\n and the_hash_algo variables.\n\n Will merge to 'master'.\n source: <944c2331-4dec-4c98-9059-f41dc204ed86@web.de>\n\n\n* aa/reap-transport-child-processes (2026-03-12) 1 commit\n . transport-helper, connect: use clean_on_exit to reap children on abnormal exit\n\n A few code paths that spawned child processes for network\n connection weren't wait(2)ing for their children and letting \"init\"\n reap them instead; they have been tightened.\n\n CI failures on Windows in t0061.24?\n cf. <20260318040423.GA2858991@coredump.intra.peff.net>\n source: <20260312214945.4050010-1-cshung@gmail.com>\n\n\n* ej/ref-transaction-hook-preparing (2026-03-16) 1 commit\n (merged to 'next' on 2026-03-20 at f9b8fbb0dc)\n + refs: add 'preparing' phase to the reference-transaction hook\n\n The reference-transaction hook was taught to be triggered before\n taking locks on references in the \"preparing\" phase.\n\n Will merge to 'master'.\n source: <20260317023624.43070-2-eric.peijian@gmail.com>\n\n\n* hn/git-checkout-m-with-stash (2026-03-17) 4 commits\n - checkout: -m (--merge) uses autostash when switching branches\n - sequencer: teach autostash apply to take optional conflict marker labels\n - sequencer: allow create_autostash to run silently\n - stash: add --ours-label, --theirs-label, --base-label for apply\n\n \"git checkout -m another-branch\" was invented to deal with local\n changes to paths that are different between the current and the new\n branch, but it gave only one chance to resolve conflicts. The command\n was taught to create a stash to save the local changes.\n\n Needs review.\n source: \n\n\n* kh/name-rev-custom-format (2026-03-20) 2 commits\n - name-rev: learn --format=\n - name-rev: wrap both blocks in braces\n\n \"git name-rev\" learned to use custom format instead of the object\n name in an extended SHA-1 expression form.\n\n Comments?\n source: \n\n\n* pw/worktree-reduce-the-repository (2026-03-15) 3 commits\n - worktree: reject NULL worktree in get_worktree_git_dir()\n - worktree add: stop reading \".git/HEAD\"\n - worktree: remove \"the_repository\" from is_current_worktree()\n\n Reduce the reference to the_repository in the worktree subsystem.\n\n Expecting review responses.\n cf. \n source: \n\n\n* jw/apply-corrupt-location (2026-03-17) 3 commits\n (merged to 'next' on 2026-03-23 at 18e9b8f91f)\n + apply: report input location in binary and garbage patch errors\n + apply: report input location in header parsing errors\n + apply: report the location of corrupt patches\n\n \"git apply\" now reports the name of the input file along with the\n line number when it encounters a corrupt patch, and correctly\n resets the line counter when processing multiple patch files.\n\n Will merge to 'master'.\n source: <20260317162321.71812-1-jerrywang183@yahoo.com>\n\n\n* mf/format-patch-commit-list-format (2026-03-23) 9 commits\n (merged to 'next' on 2026-03-24 at 0f5b6702eb)\n + format-patch: --commit-list-format without prefix\n + format-patch: add preset for --commit-list-format\n + format-patch: wrap generate_commit_list_cover()\n + format.commitListFormat: strip meaning from empty\n + docs/pretty-formats: add %(count) and %(total)\n + format-patch: rename --cover-letter-format option\n + format-patch: refactor generate_commit_list_cover\n + pretty.c: better die message %(count) and %(total)\n + Merge branch 'mf/format-patch-cover-letter-format' into mf/format-patch-commit-list-format\n (this branch uses mf/format-patch-cover-letter-format.)\n\n Improve the recently introduced `git format-patch\n --commit-list-format` (formerly `--cover-letter-format`) option,\n including a new \"modern\" preset and better CLI ergonomics.\n\n Will merge to 'master'.\n source: \n\n\n* js/parseopt-subcommand-autocorrection (2026-03-16) 10 commits\n - doc: document autocorrect API\n - parseopt: add tests for subcommand autocorrection\n - parseopt: enable subcommand autocorrection for git-remote and git-notes\n - parseopt: autocorrect mistyped subcommands\n - autocorrect: provide config resolution API\n - autocorrect: rename AUTOCORRECT_SHOW to AUTOCORRECT_HINT\n - autocorrect: use mode and delay instead of magic numbers\n - help: move tty check for autocorrection to autocorrect.c\n - help: make autocorrect handling reusable\n - parseopt: extract subcommand handling from parse_options_step()\n\n The parse-options library learned to auto-correct misspelled\n subcommand names.\n\n Expecting review responses.\n cf. \n source: \n\n\n* mf/apply-p-no-atoi (2026-03-15) 1 commit\n (merged to 'next' on 2026-03-20 at 70a0a4313b)\n + apply.c: fix -p argument parsing\n\n \"git apply -p\" parses more carefully now.\n\n Will merge to 'master'.\n source: <20260316005120.7079-1-mroik@delayed.space>\n\n\n* ps/build-tweaks (2026-03-18) 8 commits\n (merged to 'next' on 2026-03-20 at fb53cf619a)\n + meson: precompile \"git-compat-util.h\"\n + meson: compile compatibility sources separately\n + git-compat-util.h: move warning infra to prepare for PCHs\n + builds: move build scripts into \"tools/\"\n + contrib: move \"update-unicode.sh\" script into \"tools/\"\n + contrib: move \"coverage-diff.sh\" script into \"tools/\"\n + contrib: move \"coccinelle/\" directory into \"tools/\"\n + Introduce new \"tools/\" directory\n (this branch is used by rs/use-strvec-pushv.)\n\n Tweak the build infrastructure by moving tools around.\n\n Will merge to 'master'.\n source: <20260319-b4-pks-build-infra-improvements-v3-0-82f5fb3edc3f@pks.im>\n\n\n* ps/object-counting (2026-03-12) 7 commits\n (merged to 'next' on 2026-03-17 at 8d3d9a1374)\n + odb: introduce generic object counting\n + odb/source: introduce generic object counting\n + object-file: generalize counting objects\n + object-file: extract logic to approximate object count\n + packfile: extract logic to count number of objects\n + odb: stop including \"odb/source.h\"\n + Merge branch 'ps/odb-sources' into ps/object-counting\n (this branch is used by ps/odb-generic-object-name-handling.)\n\n The logic to count objects has been cleaned up.\n\n Will merge to 'master'.\n source: <20260312-b4-pks-odb-source-count-objects-v2-0-5914f69256bf@pks.im>\n\n\n* kh/doc-interpret-trailers-1 (2026-03-16) 4 commits\n (merged to 'next' on 2026-03-20 at 6acc8b5a8a)\n + interpret-trailers: use placeholder instead of *\n + doc: config: convert trailers section to synopsis style\n + doc: interpret-trailers: normalize and fill out options\n + doc: interpret-trailers: convert to synopsis style\n\n Doc updates.\n\n Will merge to 'master'.\n source: \n\n\n* mm/line-log-use-standard-diff-output (2026-03-16) 4 commits\n - doc: note that -L supports patch formatting and pickaxe options\n - t4211: add tests for -L with standard diff options\n - line-log: route -L output through the standard diff pipeline\n - line-log: fix crash when combined with pickaxe options\n\n The way the \"git log -L:\" feature is bolted onto the\n log/diff machinery is being reworked a bit to make the feature\n compatible with more diff options, like -S/G.\n\n Needs review.\n source: \n\n\n* ar/config-hook-cleanups (2026-03-20) 11 commits\n - hook: show disabled hooks in \"git hook list\"\n - hook: show config scope in git hook list\n - hook: introduce hook_config_cache_entry for per-hook data\n - t1800: add test to verify hook execution ordering\n - hook: make consistent use of friendly-name in docs\n - hook: replace hook_list_clear() -> string_list_clear_func()\n - hook: detect & emit two more bugs\n - hook: rename cb_data_free/alloc -> hook_data_free/alloc\n - hook: fix minor style issues\n - hook: move unsorted_string_list_remove() to string-list.[ch]\n - Merge branch 'ar/config-hooks' into ar/config-hook-cleanups\n (this branch is used by ar/parallel-hooks.)\n\n Code clean-up around the recent \"hooks defined in config\" topic.\n\n Expecting a reroll?\n cf. \n source: <20260320115211.177351-1-adrian.ratiu@collabora.com>\n\n\n* ab/clone-default-object-filter (2026-03-14) 1 commit\n - clone: add clone..defaultObjectFilter config\n\n \"git clone\" learns to pay attention to \"clone..defaultObjectFilter\"\n configuration and behave as if the \"--filter=\" option\n was given on the command line.\n\n Expecting review responses.\n cf. \n source: \n\n\n* jc/neuter-sideband-fixup (2026-03-05) 6 commits\n (merged to 'next' on 2026-03-13 at 5a4098b0cd)\n + sideband: drop 'default' configuration\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 (this branch is used by jc/neuter-sideband-post-3.0.)\n\n Try to resurrect and reboot a stalled \"avoid sending risky escape\n sequences taken from sideband to the terminal\" topic by Dscho. The\n plan is to keep it in 'next' long enough to see if anybody screams\n with the \"everything dropped except for ANSI color escape sequences\"\n default.\n\n Will keep in 'next' a bit longer than usual.\n source: <20260305233452.3727126-1-gitster@pobox.com>\n\n\n* jc/neuter-sideband-post-3.0 (2026-03-05) 2 commits\n - sideband: delay sanitizing by default to Git v3.0\n - Merge branch 'jc/neuter-sideband-fixup' into jc/neuter-sideband-post-3.0\n (this branch uses jc/neuter-sideband-fixup.)\n\n The final step, split from earlier attempt by Dscho, to loosen the\n sideband restriction for now and tighten later at Git v3.0 boundary.\n\n On hold, until jc/neuter-sideband-fixup cooks long enough in 'next'.\n (this branch uses jc/neuter-sideband-fixup.)\n source: <20260305233452.3727126-8-gitster@pobox.com>\n\n\n* cs/subtree-split-recursion (2026-03-05) 3 commits\n - contrib/subtree: reduce recursion during split\n - contrib/subtree: functionalize split traversal\n - contrib/subtree: reduce function side-effects\n\n When processing large history graphs on Debian or Ubuntu, \"git\n subtree\" can die with a \"recursion depth reached\" error.\n\n Comments?\n source: <20260305-cs-subtree-split-recursion-v2-0-7266be870ba9@howdoi.land>\n\n\n* pt/promisor-lazy-fetch-no-recurse (2026-03-11) 1 commit\n - promisor-remote: prevent lazy-fetch recursion in child fetch\n\n The mechanism to avoid recursive lazy-fetch from promisor remotes\n was not propagated properly to child \"git fetch\" processes, which\n has been corrected.\n\n Comments?\n source: \n\n\n* mf/format-patch-cover-letter-format (2026-03-06) 5 commits\n (merged to 'next' on 2026-03-09 at e872adca7b)\n + docs: add usage for the cover-letter fmt feature\n + format-patch: add commitListFormat config\n + format-patch: add ability to use alt cover format\n + format-patch: move cover letter summary generation\n + pretty.c: add %(count) and %(total) placeholders\n (this branch is used by mf/format-patch-commit-list-format.)\n\n \"git format-patch --cover-letter\" learns to use a simpler format\n instead of the traditional shortlog format to list its commits with\n a new --cover-letter-format option and format.commitListFormat\n configuration variable.\n\n Waiting for the follow-on topic.\n source: \n\n\n* pt/fsmonitor-linux (2026-03-04) 12 commits\n - fsmonitor: convert shown khash to strset in do_handle_client\n - fsmonitor: add tests for Linux\n - fsmonitor: add timeout to daemon stop command\n - fsmonitor: close inherited file descriptors and detach in daemon\n - run-command: add close_fd_above_stderr option\n - fsmonitor: implement filesystem change listener for Linux\n - fsmonitor: rename fsm-settings-darwin.c to fsm-settings-unix.c\n - fsmonitor: rename fsm-ipc-darwin.c to fsm-ipc-unix.c\n - fsmonitor: use pthread_cond_timedwait for cookie wait\n - compat/win32: add pthread_cond_timedwait\n - fsmonitor: fix hashmap memory leak in fsmonitor_run_daemon\n - fsmonitor: fix khash memory leak in do_handle_client\n\n The fsmonitor daemon has been implemented for Linux.\n\n Waiting for the rerolls to slow down?\n cf. \n source: \n\n\n* sa/replay-revert (2026-03-12) 2 commits\n - replay: add --revert mode to reverse commit changes\n - sequencer: extract revert message formatting into shared function\n\n \"git replay\" (experimental) learns, in addition to \"pick\" and\n \"replay\", a new operating mode \"revert\".\n\n Expecting review responses.\n cf. <87pl53si56.fsf@iotcl.com>\n source: <20260313054035.26605-1-siddharthasthana31@gmail.com>\n\n\n* vp/http-rate-limit-retries (2026-03-17) 3 commits\n (merged to 'next' on 2026-03-24 at 9cb4ec5fad)\n + http: add support for HTTP 429 rate limit retries\n + strbuf_attach: fix call sites to pass correct alloc\n + strbuf: pass correct alloc to strbuf_attach() in strbuf_reencode()\n\n The HTTP transport learned to react to \"429 Too Many Requests\".\n\n Will merge to 'master'.\n cf. \n source: \n\n\n* ar/parallel-hooks (2026-03-20) 11 commits\n - hook: add hook..enabled switch\n - hook: warn when hook..jobs is set\n - hook: add per-event jobs config\n - hook: add -j/--jobs option to git hook run\n - hook: mark non-parallelizable hooks\n - hook: allow pre-push parallel execution\n - hook: allow parallel hook execution\n - hook: parse the hook.jobs config\n - config: add a repo_config_get_uint() helper\n - repository: fix repo_init() memleak due to missing _clear()\n - Merge branch 'ar/config-hook-cleanups' into ar/parallel-hooks\n (this branch uses ar/config-hook-cleanups.)\n\n Needs review.\n source: <20260320135311.331463-1-adrian.ratiu@collabora.com>\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 the xdiff/ codebase to work with Rust\n\n Expecting a reroll.\n cf. \n source: \n\n\n* tb/incremental-midx-part-3.2 (2026-02-24) 17 commits\n (merged to 'next' on 2026-03-18 at 7f995e23bb)\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 + 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\n Further work on incremental repacking using MIDX/bitmap\n\n Will merge to 'master'.\n source: \n\n\n* js/macos-homebrew-forgets-reg-enhanced (2026-03-20) 1 commit\n . osx-clang: work around Homebrew's clang lacking REG_ENHANCED\n\n The build on macOS with Clang is fixed to work around a Homebrew change\n that exposed an issue with missing REG_ENHANCED.\n\n No longer needed.\n cf. <6c108696-2d41-4fa1-9662-fbf6db97f767@web.de>\n cf. <458ad3c1-96df-4575-ee42-e6eb754f25f6@gmx.de>\n source: \n\n--------------------------------------------------\n[Discarded]\n\n* js/neuter-sideband (2026-02-03) 6 commits\n . sideband: delay sanitizing by default to Git v3.0\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 Superseded by 'jc/neuter-sideband-fixup', which reuses most of the patches.\n cf. \n source: \n\n\n* bc/rev-parse-parseopt-help-exit-code (2026-03-16) 1 commit\n . rev-parse: have --parseopt callers exit 0 on --help\n\n `rev-parse --parseopt` now includes \"exit 0\" in its output when the\n user asks for help, ensuring that scripts using the recommended `eval`\n pattern exit successfully.\n\n Need to step back and rethink how exit code should look like.\n cf. <20260317150759.GA9975@coredump.intra.peff.net>\n source: <20260316220742.1286157-1-sandals@crustytoothpaste.net>\n"},{"id":"539896","messageId":"20260325061357.GA3772970@coredump.intra.peff.net","threadId":"65348","inReplyTo":"xmqqldfgy1ye.fsf@gitster.g","subject":"Re: What's cooking in git.git (Mar 2026, #10)","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2026-03-25T06:13:57Z","receivedAt":"2026-03-25T06:13:58Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":null},"body":"On Tue, Mar 24, 2026 at 09:20:41PM -0700, Junio C Hamano wrote:\n\n> * aa/reap-transport-child-processes (2026-03-12) 1 commit\n> . transport-helper, connect: use clean_on_exit to reap children on abnormal exit\n> \n> A few code paths that spawned child processes for network\n> connection weren't wait(2)ing for their children and letting \"init\"\n> reap them instead; they have been tightened.\n> \n> CI failures on Windows in t0061.24?\n> cf. <20260318040423.GA2858991@coredump.intra.peff.net>\n> source: <20260312214945.4050010-1-cshung@gmail.com>\n\nAfter a grueling session with tmate to connect to a GitHub Actions\nWindows runner, I can confirm that the patch below fixes the failure.\n\nI had a lingering worry that maybe the test was a canary in the coal\nmine, telling us that other real-world cases may be mad about getting\nkill()ed. But after looking at it, I'm not sure. The fake ssh command is\n_so_ fake here that it produces garbage output immediately and is\nkilled before even doing its logging. A real failure would happen\nfarther along in the process. And presumably a real ssh client that has\ncleanup to do would catch the signal and do that cleanup.\n\nSo...it's probably OK to fix the test and proceed with graduating the\ntopic, I think?\n\nAnyway, here's the fix I came up with. But see below the --- line, too.\n\n-- >8 --\nSubject: [PATCH] t0061: simplify .bat test\n\nThe test added by 71f4960b91 (t0061: fix test for argv[0] with spaces\n(MINGW only), 2019-10-01) checks that we can use a .bat file with spaces\nas GIT_SSH.\n\nThis is a good test in the sense that it's how the original bug was\ndetected. And as the commit message there describes, there are some\nelements of the bug that are likely to come up with GIT_SSH and not\nelsewhere: namely that in addition to the .bat file having spaces, we\nmust pass an argument with spaces (which happens naturally with ssh,\nsince we pass the upload-pack shell command for the other side to run).\n\nBut using GIT_SSH does complicate matters:\n\n 1. We actually run the ssh command _twice_, once to probe the ssh\n variant with \"-G\" in fill_ssh_args(), and then a second time to\n actually make the connection. So we have to account for that when\n checking the output.\n\n 2. Our fake ssh .bat file does not actually run ssh. So we expect the\n command to fail, but not before the .bat file has touched the \"out\"\n marker file that tells us it has run.\n\n This works now, but is fragile. In particular, the .bat file by\n default will echo commands it runs to stdout. From the perspective\n of the parent Git process, this is protocol-breaking garbage, and\n upon seeing it will die().\n\n That is OK for now because we don't bother to do any cleanup of the\n child process. But there is a patch under discussion, dd3693eb08\n (transport-helper, connect: use clean_on_exit to reap children on\n abnormal exit, 2026-03-12), which causes us to kill() the .bat\n process. This happens before it actually touches the \"out\" file,\n causing the test to fail.\n\nWe can simplify this by just using the \"test-tool run-command\" helper.\nThat lets us run whatever command we like with the arguments we want.\nThe argument here has a space, which is enough to trigger the original\nbug that 71f4960b91 was testing. I verified that by reverting eb7c786314\n(mingw: support spawning programs containing spaces in their names,\n2019-07-16), the original fix, and confirming that the test fails (but\nsucceeds without the revert).\n\nSigned-off-by: Jeff King \n---\nOne thing that puzzled me but that I figured out while writing the\ncommit message above is why the .bat file was writing garbage to stdout\nin the first place. But then through the haze of DOS memories, I\nrecalled the horror of having to put \"@echo off\" at the top of every\nbatch file.\n\nSo probably the smallest fix is to just add that to the start of the\n.bat file, or even just put \"@\" at the start of the single command in\nthe file. That would suppress the extra stdout, and Git would not\nrealize the bogus ssh command is failing until it exits without writing\nanything (which is after it has touched the \"out\" file).\n\nI didn't have the stomach or patience to spin up the tmate environment\nagain and test it, though. I do like how much simpler the test gets with\nthe t/helper program, but arguably using GIT_SSH is more realistic. I\ndunno.\n\n t/t0061-run-command.sh | 12 ++----------\n 1 file changed, 2 insertions(+), 10 deletions(-)\n\ndiff --git a/t/t0061-run-command.sh b/t/t0061-run-command.sh\nindex 2f77fde0d9..60cfe65979 100755\n--- a/t/t0061-run-command.sh\n+++ b/t/t0061-run-command.sh\n@@ -287,16 +287,8 @@ test_expect_success MINGW 'can spawn .bat with argv[0] containing spaces' '\n \trm -f out &&\n \techo \"echo %* >>out\" >\"$bat\" &&\n \n-\t# Ask git to invoke .bat; clone will fail due to fake SSH helper\n-\ttest_must_fail env GIT_SSH=\"$bat\" git clone myhost:src ssh-clone &&\n-\n-\t# Spawning .bat can fail if there are two quoted cmd.exe arguments.\n-\t# .bat itself is first (due to spaces in name), so just one more is\n-\t# needed to verify. GIT_SSH will invoke .bat multiple times:\n-\t# 1) -G myhost\n-\t# 2) myhost \"git-upload-pack src\"\n-\t# First invocation will always succeed. Test the second one.\n-\tgrep \"git-upload-pack\" out\n+\ttest-tool run-command run-command \"$bat\" \"arg with spaces\" &&\n+\ttest_grep \"arg with spaces\" out\n '\n \n test_done\n-- \n2.53.0.1057.g8b84bc5fb6\n\n"},{"id":"539921","messageId":"CAPYXD65-LwXrZSAtGmbj-O4nW7WMcrJ_D8HtNtW5WZY2fLbGqQ@mail.gmail.com","threadId":"65348","inReplyTo":"xmqqldfgy1ye.fsf@gitster.g","subject":"Re: What's cooking in git.git (Mar 2026, #10)","fromName":"Shreyansh Paliwal","fromEmail":"shreyanshpaliwalcmsmn@gmail.com","sentAt":"2026-03-25T08:33:02Z","receivedAt":"2026-03-25T08:33:14Z","isPatch":false,"sender":{"key":"shreyanshpaliwalcmsmn@gmail.com","avatar":null},"body":"> * sp/add-patch-with-fewer-the-repository (2026-03-17) 1 commit\n> - add-patch: use repository instance from add_i_state instead of the_repository\n>\n> Reduce dependency on `the_repository` in add-patch.c file.\n>\n> Needs review.\n> source: <20260317155230.619378-1-shreyanshpaliwalcmsmn@gmail.com>\n\nI think this was considered ready in the previous 'What's cooking in git.git',\nso the status can be changed now.\n\nThanks,\nShreyansh\n"},{"id":"539989","messageId":"xmqq1ph7u1sm.fsf@gitster.g","threadId":"65348","inReplyTo":"CAPYXD65-LwXrZSAtGmbj-O4nW7WMcrJ_D8HtNtW5WZY2fLbGqQ@mail.gmail.com","subject":"Re: What's cooking in git.git (Mar 2026, #10)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-03-25T19:50:01Z","receivedAt":"2026-03-25T19:50:06Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":null},"body":"Shreyansh Paliwal writes:\n\n>> * sp/add-patch-with-fewer-the-repository (2026-03-17) 1 commit\n>> - add-patch: use repository instance from add_i_state instead of the_repository\n>>\n>> Reduce dependency on `the_repository` in add-patch.c file.\n>>\n>> Needs review.\n>> source: <20260317155230.619378-1-shreyanshpaliwalcmsmn@gmail.com>\n>\n> I think this was considered ready in the previous 'What's cooking in git.git',\n> so the status can be changed now.\n\nThis was listed in the new topics section in issue #07 (Mar 19) but\nI do not recall updating its status in any later issue. The only\nchange was in issue #08 (Mar 21) in which the topic was moved from\nnew to cooking without changing any status.\n\nThe only comment the patch got was from me about interaction with\nother topics in flight, and there was no discussion or comments on\nwhat the patch wants to do makes sense, or if the way how the patch\ndoes so is correct, which should be the real review.\n\nAnd I do not consider my single reading alone a sufficient review\nmost of the time.\n"},{"id":"540114","messageId":"e33142cb-1ec3-468f-8080-ba3bad79ae25@app.fastmail.com","threadId":"65348","inReplyTo":"xmqqldfgy1ye.fsf@gitster.g","subject":"kh/name-rev-custom-format","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2026-03-26T18:07:57Z","receivedAt":"2026-03-26T18:08:18Z","isPatch":false,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"On Wed, Mar 25, 2026, at 05:20, Junio C Hamano wrote:\n> * kh/name-rev-custom-format (2026-03-20) 2 commits\n> - name-rev: learn --format=\n> - name-rev: wrap both blocks in braces\n>\n> \"git name-rev\" learned to use custom format instead of the object\n> name in an extended SHA-1 expression form.\n>\n> Comments?\n> source: \n\nI’m working on rewriting the functionality in the form of a new builtin\ngit-format-rev(1) that lives in `builtin/name-rev.c`.\n"},{"id":"540115","messageId":"xmqqtsu2pgu9.fsf@gitster.g","threadId":"65348","inReplyTo":"e33142cb-1ec3-468f-8080-ba3bad79ae25@app.fastmail.com","subject":"Re: kh/name-rev-custom-format","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-03-26T18:48:30Z","receivedAt":"2026-03-26T18:48:33Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":null},"body":"\"Kristoffer Haugsbakk\" writes:\n\n> On Wed, Mar 25, 2026, at 05:20, Junio C Hamano wrote:\n>> * kh/name-rev-custom-format (2026-03-20) 2 commits\n>> - name-rev: learn --format=\n>> - name-rev: wrap both blocks in braces\n>>\n>> \"git name-rev\" learned to use custom format instead of the object\n>> name in an extended SHA-1 expression form.\n>>\n>> Comments?\n>> source: \n>\n> I’m working on rewriting the functionality in the form of a new builtin\n> git-format-rev(1) that lives in `builtin/name-rev.c`.\n\nBy the way, why do we want yet another builtin in the first place?\nWouldn't this be done as a new option to \"git log\", for example?\n"},{"id":"540129","messageId":"8c9dd9f9-4d41-4901-b1fb-080e4e73b40a@app.fastmail.com","threadId":"65348","inReplyTo":"xmqqtsu2pgu9.fsf@gitster.g","subject":"Re: kh/name-rev-custom-format","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2026-03-26T19:22:46Z","receivedAt":"2026-03-26T19:23:08Z","isPatch":false,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"On Thu, Mar 26, 2026, at 19:48, Junio C Hamano wrote:\n> \"Kristoffer Haugsbakk\" writes:\n>\n>> On Wed, Mar 25, 2026, at 05:20, Junio C Hamano wrote:\n>>> * kh/name-rev-custom-format (2026-03-20) 2 commits\n>>> - name-rev: learn --format=\n>>> - name-rev: wrap both blocks in braces\n>>>\n>>> \"git name-rev\" learned to use custom format instead of the object\n>>> name in an extended SHA-1 expression form.\n>>>\n>>> Comments?\n>>> source: \n>>\n>> I’m working on rewriting the functionality in the form of a new builtin\n>> git-format-rev(1) that lives in `builtin/name-rev.c`.\n>\n> By the way, why do we want yet another builtin in the first place?\n\nI didn’t want another builtin. I looked at the options and didn’t find\nanything that fit the described use case.\n\nWith git-name-rev(1) it looked like formatting options could crowd up\nthe place.\n\n> Wouldn't this be done as a new option to \"git log\", for example?\n\nOkay with me.\n\ngit-log(1) blocks until I have closed stdin and effectively dedups\nthe output.\n\n git log --oneline --stdin --no-walk\n HEAD\n HEAD\n HEAD\n ^D\n \n\nSo if an option could tweak it to instead (1) give one output per line\n(like git-name-rev(1)) and (2) not deduplicate (well, follows from (1))\nthen the problem seems solved.\n\nThinking out loud here.\n"},{"id":"540133","messageId":"xmqqecl6pe8u.fsf@gitster.g","threadId":"65348","inReplyTo":"8c9dd9f9-4d41-4901-b1fb-080e4e73b40a@app.fastmail.com","subject":"Re: kh/name-rev-custom-format","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-03-26T19:44:33Z","receivedAt":"2026-03-26T19:44:35Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":null},"body":"\"Kristoffer Haugsbakk\" writes:\n\n> With git-name-rev(1) it looked like formatting options could crowd up\n> the place.\n>\n>> Wouldn't this be done as a new option to \"git log\", for example?\n>\n> Okay with me.\n>\n> git-log(1) blocks until I have closed stdin and effectively dedups\n> the output.\n\nAh, I forgot about the \"--stdin\" mode. That makes it a non-starter\nX-<. Sorry about the noise.\n\n>\n> git log --oneline --stdin --no-walk\n> HEAD\n> HEAD\n> HEAD\n> ^D\n> \n>\n> So if an option could tweak it to instead (1) give one output per line\n> (like git-name-rev(1)) and (2) not deduplicate (well, follows from (1))\n> then the problem seems solved.\n>\n> Thinking out loud here.\n"}]}