* What's cooking in git.git (Mar 2026, #10)
@ 2026-03-25 4:20 Junio C Hamano
2026-03-25 6:13 ` Jeff King
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: Junio C Hamano @ 2026-03-25 4:20 UTC (permalink / raw)
To: git
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']
* dd/cocci-do-not-pass-strbuf-by-value (2026-03-15) 3 commits
(merged to 'next' on 2026-03-18 at a2ffed1127)
+ stash: do not pass strbuf by value
+ coccinelle: detect struct strbuf passed by value
+ Merge branch 'dd/list-objects-filter-options-wo-strbuf-split' into dd/cocci-do-not-pass-strbuf-by-value
Add a coccinelle rule to break the build when "struct strbuf" gets
passed by value.
source: <20260315094445.19849-1-deveshigurgaon@gmail•com>
* gj/user-manual-fix-grep-example (2026-03-16) 1 commit
(merged to 'next' on 2026-03-17 at dbf9137a9d)
+ doc: fix git grep args order in Quick Reference
Fix an example in the user-manual.
source: <pull.2069.git.1773670536808.gitgitgadget@gmail•com>
* jk/transport-color-leakfix (2026-03-14) 1 commit
(merged to 'next' on 2026-03-17 at c2d7c74d11)
+ transport: plug leaks in transport_color_config()
Leakfix.
source: <20260314160814.GA918806@coredump•intra.peff.net>
* jt/fast-import-sign-again (2026-03-12) 3 commits
(merged to 'next' on 2026-03-17 at e04808d5f2)
+ fast-import: add mode to sign commits with invalid signatures
+ gpg-interface: allow sign_buffer() to use default signing key
+ commit: remove unused forward declaration
"git fast-import" learned to optionally replace signature on
commits whose signatures get invalidated due to replaying by
signing afresh.
source: <20260313013938.2742124-1-jltobler@gmail•com>
* mf/t0008-cleanup (2026-03-15) 1 commit
(merged to 'next' on 2026-03-17 at 2bb0e51243)
+ t0008: improve test cleanup to fix failing test
Test clean-up.
source: <20260316011544.13825-1-mroik@delayed•space>
* pb/t4200-test-path-is-helpers (2026-03-16) 1 commit
(merged to 'next' on 2026-03-17 at a78771f93e)
+ t4200: convert test -[df] checks to test_path_* helpers
Test clean-up.
source: <20260316172457.38242-1-prashantjee2025@gmail•com>
* ps/clar-wo-path-max (2026-03-16) 1 commit
(merged to 'next' on 2026-03-17 at 1d2f28a677)
+ clar: update to fix compilation on platforms without PATH_MAX
Clar (unit testing framework) update from the upstream.
source: <20260316-b4-pks-clar-without-path-max-v1-1-40b4bc91fdc0@pks•im>
* ps/history-split (2026-03-02) 8 commits
(merged to 'next' on 2026-03-17 at 456723f018)
+ builtin/history: implement "split" subcommand
+ builtin/history: split out extended function to create commits
+ cache-tree: allow writing in-memory index as tree
+ add-patch: allow disabling editing of hunks
+ add-patch: add support for in-memory index patching
+ add-patch: remove dependency on "add-interactive" subsystem
+ add-patch: split out `struct interactive_options`
+ add-patch: split out header from "add-interactive.h"
"git history" learned the "split" subcommand.
source: <20260302-pks-history-split-v1-0-444fc987a324@pks•im>
* ps/upload-pack-buffer-more-writes (2026-03-12) 10 commits
(merged to 'next' on 2026-03-18 at 138ad42ac5)
+ builtin/pack-objects: reduce lock contention when writing packfile data
+ csum-file: drop `hashfd_throughput()`
+ csum-file: introduce `hashfd_ext()`
+ sideband: use writev(3p) to send pktlines
+ wrapper: introduce writev(3p) wrappers
+ compat/posix: introduce writev(3p) wrapper
+ upload-pack: reduce lock contention when writing packfile data
+ upload-pack: prefer flushing data over sending keepalive
+ upload-pack: adapt keepalives based on buffering
+ upload-pack: fix debug statement when flushing packfile data
Reduce system overhead "git upload-pack" spends on relaying "git
pack-objects" output to the "git fetch" running on the other end of
the connection.
source: <20260313-pks-upload-pack-write-contention-v4-0-7a9668061f7f@pks•im>
* rj/pack-refs-tests-path-is-helpers (2026-03-15) 1 commit
(merged to 'next' on 2026-03-17 at 56374095e3)
+ t/pack-refs-tests: use test_path_is_missing
Test updates.
source: <20260315081032.497-1-riteshjd75@gmail•com>
* ss/t0410-delete-object-cleanup (2026-03-12) 1 commit
(merged to 'next' on 2026-03-17 at a8d41f4c1f)
+ t0410: modernize delete_object helper
Test clean-up.
source: <20260313053159.36492-1-r.siddharth.shrimali@gmail•com>
* ty/doc-diff-u-wo-number (2026-03-10) 1 commit
(merged to 'next' on 2026-03-18 at 8a410154ff)
+ diff: document -U without <n> as using default context
"git diff -U<num>" was too lenient in its command line parsing and
took an empty string as a valid <num>.
source: <20260310095017.131957-1-cat@malon•dev>
* yc/histogram-hunk-shift-fix (2026-03-02) 1 commit
(merged to 'next' on 2026-03-18 at 5e49edc821)
+ xdiff: re-diff shifted change groups when using histogram algorithm
The final clean-up phase of the diff output could turn the result of
histogram diff algorithm suboptimal, which has been corrected.
source: <pull.2120.v2.git.git.1772463265865.gitgitgadget@gmail•com>
--------------------------------------------------
[New Topics]
* jt/fast-import-signed-modes (2026-03-24) 4 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>'
Handling of signed commits and tags in fast-import has been made more
configurable.
source: <20260324215513.764739-1-jltobler@gmail•com>
--------------------------------------------------
[Cooking]
* ps/graph-lane-limit (2026-03-23) 3 commits
- graph: add documentation and tests about --graph-lane-limit
- graph: truncate graph visual output
- graph: add --graph-lane-limit option
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.
source: <20260323215935.74486-1-pabloosabaterr@gmail•com>
* 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
(this branch uses ps/build-tweaks.)
Code paths that loop over another array to push each element into a
strvec have been rewritten to use strvec_pushv() instead.
Will merge to 'master'.
source: <084f3b43-91ac-4553-8305-03944e97eaa6@web•de>
* 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.
Needs review.
source: <20260323080520.887550-1-christian.couder@gmail•com>
* kj/refspec-parsing-outside-repository (2026-03-23) 2 commits
- 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.
Will merge to 'next'?
source: <20260324015734.18470-1-jayatheerthkulkarni2005@gmail•com>
* jk/diff-highlight-identical-pairs (2026-03-17) 1 commit
(merged to 'next' on 2026-03-20 at a8aa5bd14e)
+ contrib/diff-highlight: do not highlight identical pairs
(this branch is used by jk/diff-highlight-more.)
The handling of the incomplete lines at the end by "git
diff-highlight" has been fixed.
Will merge to 'master'.
source: <20260317230223.GA716496@coredump•intra.peff.net>
* 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
(this branch uses jk/diff-highlight-identical-pairs.)
Various updates to contrib/diff-highlight, including documentation
updates, test improvements, and color configuration handling.
Will merge to 'master'.
source: <20260323060139.GA10215@coredump•intra.peff.net>
* ps/fsck-wo-the-repository (2026-03-23) 12 commits
- 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.
Needs review.
source: <20260323-b4-pks-fsck-without-the-repository-v2-0-e8dc79bca651@pks•im>
* tb/stdin-packs-excluded-but-open (2026-03-19) 5 commits
- 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.
Comments?
source: <cover.1773959041.git.me@ttaylorr•com>
* yc/path-walk-fix-error-reporting (2026-03-20) 1 commit
- 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.
Reproduction being discussed.
cf. <994f92e9-3576-455a-a142-0fefc559131c@gmail•com>
source: <20260320114823.3151961-1-ysinghcin@gmail•com>
* 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. <xmqqfr5tdbpc.fsf@gitster•g>
source: <20260320-bisect-terms-v1-1-c30c9540542a@schlaraffenlan•de>
* jc/whitespace-incomplete-line (2026-03-17) 1 commit
- apply: fix new-style empty context line triggering incomplete-line check
Fix whitespace correction for new-style empty context lines.
Needs review.
source: <xmqqldfql4hp.fsf@gitster•g>
* sp/add-patch-with-fewer-the-repository (2026-03-17) 1 commit
- add-patch: use repository instance from add_i_state instead of the_repository
Reduce dependency on `the_repository` in add-patch.c file.
Needs review.
source: <20260317155230.619378-1-shreyanshpaliwalcmsmn@gmail•com>
* ds/backfill-revs (2026-03-23) 6 commits
- 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.
Comments?
source: <pull.2070.v2.git.1774266019.gitgitgadget@gmail•com>
* jw/t2203-status-pipe-fix (2026-03-16) 1 commit
(merged to 'next' on 2026-03-23 at 521c6eb44b)
+ t2203: avoid suppressing git status exit code
Test clean-up.
Will merge to 'master'.
source: <20260317011544.65952-1-jerrywang183@yahoo•com>
* ps/commit-graph-overflow-fix (2026-03-23) 1 commit
- 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.
Waiting for review response.
cf. <xmqq1ph92pzs.fsf@gitster•g>
source: <20260324-pks-commit-graph-overflow-v2-1-843568cf8780@pks•im>
* tc/replay-down-to-root (2026-03-24) 1 commit
- replay: support replaying down from root commit
git replay now supports replaying down to the root commit.
Will merge to 'next'?
source: <20260324-toon-replay-down-to-root-v2-1-34e723489f6e@iotcl•com>
* mr/merge-file-object-id-worktree-fix (2026-03-10) 1 commit
(merged to 'next' on 2026-03-20 at 68e1ee2045)
+ merge-file: fix BUG when --object-id is used in a worktree
merge-file --object-id used to trigger a BUG when run in a linked
worktree, which has been fixed.
Will merge to 'master'.
source: <c076edd0-9057-443b-ba37-33aacde2eede@app•fastmail.com>
* rs/prio-queue-to-commit-stack (2026-03-17) 1 commit
(merged to 'next' on 2026-03-20 at 265cb7b28c)
+ use commit_stack instead of prio_queue in LIFO mode
Uses of prio_queue as a LIFO stack of commits have been written
with commit_stack.
Will merge to 'master'.
source: <05fc946f-6670-46e9-a058-231ee464029d@web•de>
* jw/object-name-bitset-to-enum (2026-03-18) 1 commit
(merged to 'next' on 2026-03-23 at 881af371ef)
+ object-name: turn INTERPRET_BRANCH_* constants into enum values
The unsigned integer that is used as an bitset to specify the kind
of branches interpret_branch_name() function has been changed to
use a dedicated enum type.
Will merge to 'master'.
source: <20260318190942.22595-1-jerrywang183@yahoo•com>
* ai/t2107-test-path-is-helpers (2026-03-18) 1 commit
(merged to 'next' on 2026-03-23 at 56d10e5f76)
+ t2107: modernize path existence check
Test cleanup.
Will merge to 'master'.
source: <pull.2071.v2.git.1773864455956.gitgitgadget@gmail•com>
* gi/doc-boolean-config-typofix (2026-03-18) 1 commit
(merged to 'next' on 2026-03-20 at 8810624798)
+ doc: add missing space on git-config page
Doc typofix.
Will merge to 'master'.
source: <20260318210020.759128-1-gabl@gabl•ink>
* ua/push-remote-group (2026-03-18) 2 commits
- 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 (hopefully small and final) reroll?
cf. <20260318204028.1010487-1-usmanakinyemi202@gmail•com>
source: <20260318204028.1010487-1-usmanakinyemi202@gmail•com>
* jc/rerere-modern-strbuf-handling (2026-03-19) 2 commits
(merged to 'next' on 2026-03-21 at 919b766afc)
+ cocci: strbuf.buf is never NULL
+ rerere: update to modern representation of empty strbufs
Code clean-up overdue by 19 years.
Will merge to 'master'.
source: <xmqq341wnvbk.fsf@gitster•g>
source: <xmqq4imbigvt.fsf@gitster•g>
* ps/odb-generic-object-name-handling (2026-03-20) 16 commits
- 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 uses ps/object-counting.)
Object name handling (disambiguation and abbreviation) has been
refactored to be backend-generic, moving logic into the respective
object database backends.
Comments?
source: <20260320-b4-pks-odb-source-abbrev-v2-0-fe65dcd8c735@pks•im>
* rs/ahead-behind-cleanup-optimization (2026-03-19) 1 commit
(merged to 'next' on 2026-03-21 at 5d8b4fa265)
+ commit-reach: simplify cleanup of remaining bitmaps in ahead_behind ()
The cleanup of remaining bitmaps in "ahead_behind()" has been
simplified.
Will merge to 'master'.
source: <21adf042-2bd1-4022-8822-9ed4985122a4@web•de>
* 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.
Will merge to 'master'.
source: <20260319180803.164335-1-elkhatabibilal@gmail•com>
* rs/split-index-the-repo-fix (2026-03-19) 1 commit
(merged to 'next' on 2026-03-21 at d66850b2ce)
+ split-index: stop using the_repository and the_hash_algo
split-index.c has been updated to not use the global the_repository
and the_hash_algo variables.
Will merge to 'master'.
source: <944c2331-4dec-4c98-9059-f41dc204ed86@web•de>
* aa/reap-transport-child-processes (2026-03-12) 1 commit
. 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.
CI failures on Windows in t0061.24?
cf. <20260318040423.GA2858991@coredump•intra.peff.net>
source: <20260312214945.4050010-1-cshung@gmail•com>
* ej/ref-transaction-hook-preparing (2026-03-16) 1 commit
(merged to 'next' on 2026-03-20 at f9b8fbb0dc)
+ refs: add 'preparing' phase to the reference-transaction hook
The reference-transaction hook was taught to be triggered before
taking locks on references in the "preparing" phase.
Will merge to 'master'.
source: <20260317023624.43070-2-eric.peijian@gmail•com>
* 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: <pull.2234.v6.git.git.1773740139.gitgitgadget@gmail•com>
* 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: <V2_CV_name-rev_--format.51b@msgid•xyz>
* pw/worktree-reduce-the-repository (2026-03-15) 3 commits
- 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.
Expecting review responses.
cf. <abezeNELL9SU8v82@pks•im>
source: <cover.1773591528.git.phillip.wood@dunelm•org.uk>
* jw/apply-corrupt-location (2026-03-17) 3 commits
(merged to 'next' on 2026-03-23 at 18e9b8f91f)
+ apply: report input location in binary and garbage patch errors
+ apply: report input location in header parsing errors
+ apply: report the location of corrupt patches
"git apply" now reports the name of the input file along with the
line number when it encounters a corrupt patch, and correctly
resets the line counter when processing multiple patch files.
Will merge to 'master'.
source: <20260317162321.71812-1-jerrywang183@yahoo•com>
* 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 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.
Will merge to 'master'.
source: <cover.1774284699.git.mroik@delayed•space>
* 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. <xmqqse9zo93p.fsf@gitster•g>
source: <SY0P300MB080186A23FB9582AD793F0D1CE40A@SY0P300MB0801•AUSP300.PROD.OUTLOOK.COM>
* mf/apply-p-no-atoi (2026-03-15) 1 commit
(merged to 'next' on 2026-03-20 at 70a0a4313b)
+ apply.c: fix -p argument parsing
"git apply -p<n>" parses <n> more carefully now.
Will merge to 'master'.
source: <20260316005120.7079-1-mroik@delayed•space>
* ps/build-tweaks (2026-03-18) 8 commits
(merged to 'next' on 2026-03-20 at fb53cf619a)
+ meson: precompile "git-compat-util.h"
+ meson: compile compatibility sources separately
+ git-compat-util.h: move warning infra to prepare for PCHs
+ builds: move build scripts into "tools/"
+ contrib: move "update-unicode.sh" script into "tools/"
+ contrib: move "coverage-diff.sh" script into "tools/"
+ contrib: move "coccinelle/" directory into "tools/"
+ Introduce new "tools/" directory
(this branch is used by rs/use-strvec-pushv.)
Tweak the build infrastructure by moving tools around.
Will merge to 'master'.
source: <20260319-b4-pks-build-infra-improvements-v3-0-82f5fb3edc3f@pks•im>
* ps/object-counting (2026-03-12) 7 commits
(merged to 'next' on 2026-03-17 at 8d3d9a1374)
+ odb: introduce generic object counting
+ odb/source: introduce generic object counting
+ object-file: generalize counting objects
+ object-file: extract logic to approximate object count
+ packfile: extract logic to count number of objects
+ odb: stop including "odb/source.h"
+ Merge branch 'ps/odb-sources' into ps/object-counting
(this branch is used by ps/odb-generic-object-name-handling.)
The logic to count objects has been cleaned up.
Will merge to 'master'.
source: <20260312-b4-pks-odb-source-count-objects-v2-0-5914f69256bf@pks•im>
* kh/doc-interpret-trailers-1 (2026-03-16) 4 commits
(merged to 'next' on 2026-03-20 at 6acc8b5a8a)
+ interpret-trailers: use placeholder instead of *
+ doc: config: convert trailers section to synopsis style
+ doc: interpret-trailers: normalize and fill out options
+ doc: interpret-trailers: convert to synopsis style
Doc updates.
Will merge to 'master'.
source: <V2_CV_doc_interpret-tr_synopsis.50a@msgid•xyz>
* 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.
Needs review.
source: <pull.2065.v2.git.1773714095.gitgitgadget@gmail•com>
* ar/config-hook-cleanups (2026-03-20) 11 commits
- 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
- 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.
Expecting a reroll?
cf. <acJNblQ8WRGIri0V@pks•im>
source: <20260320115211.177351-1-adrian.ratiu@collabora•com>
* 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. <abe1l8ONmFIhzaxi@pks•im>
source: <pull.2058.v6.git.1773553022381.gitgitgadget@gmail•com>
* 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: <20260305233452.3727126-1-gitster@pobox•com>
* 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: <20260305233452.3727126-8-gitster@pobox•com>
* 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: <20260305-cs-subtree-split-recursion-v2-0-7266be870ba9@howdoi•land>
* 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: <pull.2224.v3.git.git.1773238778894.gitgitgadget@gmail•com>
* 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.)
"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: <cover.1772839973.git.mroik@delayed•space>
* pt/fsmonitor-linux (2026-03-04) 12 commits
- 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.
Waiting for the rerolls to slow down?
cf. <aakyzGksiC2fhhiD@pks•im>
source: <pull.2147.v8.git.git.1772648125.gitgitgadget@gmail•com>
* sa/replay-revert (2026-03-12) 2 commits
- replay: add --revert mode to reverse commit changes
- sequencer: extract revert message formatting into shared function
"git replay" (experimental) learns, in addition to "pick" and
"replay", a new operating mode "revert".
Expecting review responses.
cf. <87pl53si56.fsf@iotcl•com>
source: <20260313054035.26605-1-siddharthasthana31@gmail•com>
* 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".
Will merge to 'master'.
cf. <ab4RIZr7b49VKjR9@nand•local>
source: <pull.2008.v6.git.1773752435.gitgitgadget@gmail•com>
* ar/parallel-hooks (2026-03-20) 11 commits
- hook: add hook.<event>.enabled switch
- 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: <20260320135311.331463-1-adrian.ratiu@collabora•com>
* en/xdiff-cleanup-3 (2026-01-03) 11 commits
. SQUASH??? cocci
. xdiff: move xdl_cleanup_records() from xprepare.c to xdiffi.c
. xdiff: remove dependence on xdlclassifier from xdl_cleanup_records()
. xdiff: replace xdfile_t.dend with xdfenv_t.delta_end
. xdiff: replace xdfile_t.dstart with xdfenv_t.delta_start
. xdiff: cleanup xdl_trim_ends()
. xdiff: use xdfenv_t in xdl_trim_ends() and xdl_cleanup_records()
. xdiff: let patience and histogram benefit from xdl_trim_ends()
. xdiff: don't waste time guessing the number of lines
. xdiff: make classic diff explicit by creating xdl_do_classic_diff()
. ivec: introduce the C side of ivec
Preparation of the xdiff/ codebase to work with Rust
Expecting a reroll.
cf. <CAH=ZcbBVSqUG89n65MBpN+HMCmmjzmADGaVnuEJn_cYN0SYknw@mail•gmail.com>
source: <pull.2156.git.git.1767379944.gitgitgadget@gmail•com>
* tb/incremental-midx-part-3.2 (2026-02-24) 17 commits
(merged to 'next' on 2026-03-18 at 7f995e23bb)
+ midx: enable reachability bitmaps during MIDX compaction
+ midx: implement MIDX compaction
+ t/helper/test-read-midx.c: plug memory leak when selecting layer
+ midx-write.c: factor fanout layering from `compute_sorted_entries()`
+ midx-write.c: enumerate `pack_int_id` values directly
+ midx-write.c: extract `fill_pack_from_midx()`
+ midx-write.c: introduce `midx_pack_perm()` helper
+ midx: do not require packs to be sorted in lexicographic order
+ midx-write.c: introduce `struct write_midx_opts`
+ midx-write.c: don't use `pack_perm` when assigning `bitmap_pos`
+ t/t5319-multi-pack-index.sh: fix copy-and-paste error in t5319.39
+ git-multi-pack-index(1): align SYNOPSIS with 'git multi-pack-index -h'
+ git-multi-pack-index(1): remove non-existent incompatibility
+ builtin/multi-pack-index.c: make '--progress' a common option
+ midx: introduce `midx_get_checksum_hex()`
+ midx: rename `get_midx_checksum()` to `midx_get_checksum_hash()`
+ midx: mark `get_midx_checksum()` arguments as const
Further work on incremental repacking using MIDX/bitmap
Will merge to 'master'.
source: <cover.1771959555.git.me@ttaylorr•com>
* 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. <6c108696-2d41-4fa1-9662-fbf6db97f767@web•de>
cf. <458ad3c1-96df-4575-ee42-e6eb754f25f6@gmx•de>
source: <d340af9e-334c-4e81-e58a-fc3dea73ebdd@gmx•de>
--------------------------------------------------
[Discarded]
* js/neuter-sideband (2026-02-03) 6 commits
. sideband: delay sanitizing by default to Git v3.0
. sideband: offer to configure sanitizing on a per-URL basis
. sideband: add options to allow more control sequences to be passed through
. sideband: do allow ANSI color sequences by default
. sideband: introduce an "escape hatch" to allow control characters
. sideband: mask control characters
Invalidate control characters in sideband messages, to avoid
terminal state getting messed up.
Superseded by 'jc/neuter-sideband-fixup', which reuses most of the patches.
cf. <xmqqv7gcnwd4.fsf@gitster•g>
source: <pull.1853.v4.git.1770113882.gitgitgadget@gmail•com>
* 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. <20260317150759.GA9975@coredump•intra.peff.net>
source: <20260316220742.1286157-1-sandals@crustytoothpaste•net>
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: What's cooking in git.git (Mar 2026, #10)
2026-03-25 4:20 What's cooking in git.git (Mar 2026, #10) Junio C Hamano
@ 2026-03-25 6:13 ` Jeff King
2026-03-25 8:33 ` Shreyansh Paliwal
2026-03-26 18:07 ` kh/name-rev-custom-format Kristoffer Haugsbakk
2 siblings, 0 replies; 9+ messages in thread
From: Jeff King @ 2026-03-25 6:13 UTC (permalink / raw)
To: Junio C Hamano; +Cc: git
On Tue, Mar 24, 2026 at 09:20:41PM -0700, Junio C Hamano wrote:
> * aa/reap-transport-child-processes (2026-03-12) 1 commit
> . 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.
>
> CI failures on Windows in t0061.24?
> cf. <20260318040423.GA2858991@coredump•intra.peff.net>
> source: <20260312214945.4050010-1-cshung@gmail•com>
After a grueling session with tmate to connect to a GitHub Actions
Windows runner, I can confirm that the patch below fixes the failure.
I had a lingering worry that maybe the test was a canary in the coal
mine, telling us that other real-world cases may be mad about getting
kill()ed. But after looking at it, I'm not sure. The fake ssh command is
_so_ fake here that it produces garbage output immediately and is
killed before even doing its logging. A real failure would happen
farther along in the process. And presumably a real ssh client that has
cleanup to do would catch the signal and do that cleanup.
So...it's probably OK to fix the test and proceed with graduating the
topic, I think?
Anyway, here's the fix I came up with. But see below the --- line, too.
-- >8 --
Subject: [PATCH] t0061: simplify .bat test
The test added by 71f4960b91 (t0061: fix test for argv[0] with spaces
(MINGW only), 2019-10-01) checks that we can use a .bat file with spaces
as GIT_SSH.
This is a good test in the sense that it's how the original bug was
detected. And as the commit message there describes, there are some
elements of the bug that are likely to come up with GIT_SSH and not
elsewhere: namely that in addition to the .bat file having spaces, we
must pass an argument with spaces (which happens naturally with ssh,
since we pass the upload-pack shell command for the other side to run).
But using GIT_SSH does complicate matters:
1. We actually run the ssh command _twice_, once to probe the ssh
variant with "-G" in fill_ssh_args(), and then a second time to
actually make the connection. So we have to account for that when
checking the output.
2. Our fake ssh .bat file does not actually run ssh. So we expect the
command to fail, but not before the .bat file has touched the "out"
marker file that tells us it has run.
This works now, but is fragile. In particular, the .bat file by
default will echo commands it runs to stdout. From the perspective
of the parent Git process, this is protocol-breaking garbage, and
upon seeing it will die().
That is OK for now because we don't bother to do any cleanup of the
child process. But there is a patch under discussion, dd3693eb08
(transport-helper, connect: use clean_on_exit to reap children on
abnormal exit, 2026-03-12), which causes us to kill() the .bat
process. This happens before it actually touches the "out" file,
causing the test to fail.
We can simplify this by just using the "test-tool run-command" helper.
That lets us run whatever command we like with the arguments we want.
The argument here has a space, which is enough to trigger the original
bug that 71f4960b91 was testing. I verified that by reverting eb7c786314
(mingw: support spawning programs containing spaces in their names,
2019-07-16), the original fix, and confirming that the test fails (but
succeeds without the revert).
Signed-off-by: Jeff King <peff@peff•net>
---
One thing that puzzled me but that I figured out while writing the
commit message above is why the .bat file was writing garbage to stdout
in the first place. But then through the haze of DOS memories, I
recalled the horror of having to put "@echo off" at the top of every
batch file.
So probably the smallest fix is to just add that to the start of the
.bat file, or even just put "@" at the start of the single command in
the file. That would suppress the extra stdout, and Git would not
realize the bogus ssh command is failing until it exits without writing
anything (which is after it has touched the "out" file).
I didn't have the stomach or patience to spin up the tmate environment
again and test it, though. I do like how much simpler the test gets with
the t/helper program, but arguably using GIT_SSH is more realistic. I
dunno.
t/t0061-run-command.sh | 12 ++----------
1 file changed, 2 insertions(+), 10 deletions(-)
diff --git a/t/t0061-run-command.sh b/t/t0061-run-command.sh
index 2f77fde0d9..60cfe65979 100755
--- a/t/t0061-run-command.sh
+++ b/t/t0061-run-command.sh
@@ -287,16 +287,8 @@ test_expect_success MINGW 'can spawn .bat with argv[0] containing spaces' '
rm -f out &&
echo "echo %* >>out" >"$bat" &&
- # Ask git to invoke .bat; clone will fail due to fake SSH helper
- test_must_fail env GIT_SSH="$bat" git clone myhost:src ssh-clone &&
-
- # Spawning .bat can fail if there are two quoted cmd.exe arguments.
- # .bat itself is first (due to spaces in name), so just one more is
- # needed to verify. GIT_SSH will invoke .bat multiple times:
- # 1) -G myhost
- # 2) myhost "git-upload-pack src"
- # First invocation will always succeed. Test the second one.
- grep "git-upload-pack" out
+ test-tool run-command run-command "$bat" "arg with spaces" &&
+ test_grep "arg with spaces" out
'
test_done
--
2.53.0.1057.g8b84bc5fb6
^ permalink raw reply related [flat|nested] 9+ messages in thread* Re: What's cooking in git.git (Mar 2026, #10)
2026-03-25 4:20 What's cooking in git.git (Mar 2026, #10) Junio C Hamano
2026-03-25 6:13 ` Jeff King
@ 2026-03-25 8:33 ` Shreyansh Paliwal
2026-03-25 19:50 ` Junio C Hamano
2026-03-26 18:07 ` kh/name-rev-custom-format Kristoffer Haugsbakk
2 siblings, 1 reply; 9+ messages in thread
From: Shreyansh Paliwal @ 2026-03-25 8:33 UTC (permalink / raw)
To: Junio C Hamano; +Cc: git
> * sp/add-patch-with-fewer-the-repository (2026-03-17) 1 commit
> - add-patch: use repository instance from add_i_state instead of the_repository
>
> Reduce dependency on `the_repository` in add-patch.c file.
>
> Needs review.
> source: <20260317155230.619378-1-shreyanshpaliwalcmsmn@gmail•com>
I think this was considered ready in the previous 'What's cooking in git.git',
so the status can be changed now.
Thanks,
Shreyansh
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: What's cooking in git.git (Mar 2026, #10)
2026-03-25 8:33 ` Shreyansh Paliwal
@ 2026-03-25 19:50 ` Junio C Hamano
0 siblings, 0 replies; 9+ messages in thread
From: Junio C Hamano @ 2026-03-25 19:50 UTC (permalink / raw)
To: Shreyansh Paliwal; +Cc: git
Shreyansh Paliwal <shreyanshpaliwalcmsmn@gmail•com> writes:
>> * sp/add-patch-with-fewer-the-repository (2026-03-17) 1 commit
>> - add-patch: use repository instance from add_i_state instead of the_repository
>>
>> Reduce dependency on `the_repository` in add-patch.c file.
>>
>> Needs review.
>> source: <20260317155230.619378-1-shreyanshpaliwalcmsmn@gmail•com>
>
> I think this was considered ready in the previous 'What's cooking in git.git',
> so the status can be changed now.
This was listed in the new topics section in issue #07 (Mar 19) but
I do not recall updating its status in any later issue. The only
change was in issue #08 (Mar 21) in which the topic was moved from
new to cooking without changing any status.
The only comment the patch got was from me about interaction with
other topics in flight, and there was no discussion or comments on
what the patch wants to do makes sense, or if the way how the patch
does so is correct, which should be the real review.
And I do not consider my single reading alone a sufficient review
most of the time.
^ permalink raw reply [flat|nested] 9+ messages in thread
* kh/name-rev-custom-format
2026-03-25 4:20 What's cooking in git.git (Mar 2026, #10) Junio C Hamano
2026-03-25 6:13 ` Jeff King
2026-03-25 8:33 ` Shreyansh Paliwal
@ 2026-03-26 18:07 ` Kristoffer Haugsbakk
2026-03-26 18:48 ` kh/name-rev-custom-format Junio C Hamano
2 siblings, 1 reply; 9+ messages in thread
From: Kristoffer Haugsbakk @ 2026-03-26 18:07 UTC (permalink / raw)
To: Junio C Hamano, git
On Wed, Mar 25, 2026, at 05:20, Junio C Hamano wrote:
> * 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: <V2_CV_name-rev_--format.51b@msgid•xyz>
I’m working on rewriting the functionality in the form of a new builtin
git-format-rev(1) that lives in `builtin/name-rev.c`.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: kh/name-rev-custom-format
2026-03-26 18:07 ` kh/name-rev-custom-format Kristoffer Haugsbakk
@ 2026-03-26 18:48 ` Junio C Hamano
2026-03-26 19:22 ` kh/name-rev-custom-format Kristoffer Haugsbakk
0 siblings, 1 reply; 9+ messages in thread
From: Junio C Hamano @ 2026-03-26 18:48 UTC (permalink / raw)
To: Kristoffer Haugsbakk; +Cc: git
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com> writes:
> On Wed, Mar 25, 2026, at 05:20, Junio C Hamano wrote:
>> * 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: <V2_CV_name-rev_--format.51b@msgid•xyz>
>
> I’m working on rewriting the functionality in the form of a new builtin
> git-format-rev(1) that lives in `builtin/name-rev.c`.
By the way, why do we want yet another builtin in the first place?
Wouldn't this be done as a new option to "git log", for example?
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: kh/name-rev-custom-format
2026-03-26 18:48 ` kh/name-rev-custom-format Junio C Hamano
@ 2026-03-26 19:22 ` Kristoffer Haugsbakk
2026-03-26 19:44 ` kh/name-rev-custom-format Junio C Hamano
0 siblings, 1 reply; 9+ messages in thread
From: Kristoffer Haugsbakk @ 2026-03-26 19:22 UTC (permalink / raw)
To: Junio C Hamano; +Cc: git
On Thu, Mar 26, 2026, at 19:48, Junio C Hamano wrote:
> "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com> writes:
>
>> On Wed, Mar 25, 2026, at 05:20, Junio C Hamano wrote:
>>> * 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: <V2_CV_name-rev_--format.51b@msgid•xyz>
>>
>> I’m working on rewriting the functionality in the form of a new builtin
>> git-format-rev(1) that lives in `builtin/name-rev.c`.
>
> By the way, why do we want yet another builtin in the first place?
I didn’t want another builtin. I looked at the options and didn’t find
anything that fit the described use case.
With git-name-rev(1) it looked like formatting options could crowd up
the place.
> Wouldn't this be done as a new option to "git log", for example?
Okay with me.
git-log(1) blocks until I have closed stdin and effectively dedups
the output.
git log --oneline --stdin --no-walk
HEAD
HEAD
HEAD
^D
<HEAD is listed one time>
So if an option could tweak it to instead (1) give one output per line
(like git-name-rev(1)) and (2) not deduplicate (well, follows from (1))
then the problem seems solved.
Thinking out loud here.
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: kh/name-rev-custom-format
2026-03-26 19:22 ` kh/name-rev-custom-format Kristoffer Haugsbakk
@ 2026-03-26 19:44 ` Junio C Hamano
0 siblings, 0 replies; 9+ messages in thread
From: Junio C Hamano @ 2026-03-26 19:44 UTC (permalink / raw)
To: Kristoffer Haugsbakk; +Cc: git
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com> writes:
> With git-name-rev(1) it looked like formatting options could crowd up
> the place.
>
>> Wouldn't this be done as a new option to "git log", for example?
>
> Okay with me.
>
> git-log(1) blocks until I have closed stdin and effectively dedups
> the output.
Ah, I forgot about the "--stdin" mode. That makes it a non-starter
X-<. Sorry about the noise.
>
> git log --oneline --stdin --no-walk
> HEAD
> HEAD
> HEAD
> ^D
> <HEAD is listed one time>
>
> So if an option could tweak it to instead (1) give one output per line
> (like git-name-rev(1)) and (2) not deduplicate (well, follows from (1))
> then the problem seems solved.
>
> Thinking out loud here.
^ permalink raw reply [flat|nested] 9+ messages in thread
* What's cooking in git.git (May 2026, #02)
@ 2026-05-11 3:08 Junio C Hamano
2026-05-11 13:22 ` kh/name-rev-custom-format Kristoffer Haugsbakk
0 siblings, 1 reply; 9+ messages in thread
From: Junio C Hamano @ 2026-05-11 3:08 UTC (permalink / raw)
To: git
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).
The first batch of topics marked for graduation for quite a while
since 2.54-rc2 have all been merged to 'master'.
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']
* ar/parallel-hooks (2026-04-10) 13 commits
(merged to 'next' on 2026-04-13 at 0a6acf0d17)
+ t1800: test SIGPIPE with parallel hooks
+ 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()
Hook scripts defined via the configuration system can now be
configured to run in parallel.
source: <20260410090608.75283-1-adrian.ratiu@collabora•com>
* bc/rust-by-default (2026-04-09) 4 commits
(merged to 'next' on 2026-04-23 at fb9310bfae)
+ Enable Rust by default
+ Linux: link against libdl
+ ci: install cargo on Alpine
+ docs: update version with default Rust support
Rust support is enabled by default (but still allows opting out) in
some future version of Git.
source: <20260409224434.1861422-1-sandals@crustytoothpaste•net>
* cc/promisor-auto-config-url (2026-04-07) 10 commits
(merged to 'next' on 2026-04-13 at 289fcba081)
+ t5710: use proper file:// URIs for absolute paths
+ 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: refactor should_accept_remote() control flow
+ promisor-remote: reject empty name or URL in advertised remote
+ promisor-remote: clarify that a remote is ignored
+ promisor-remote: pass config entry to all_fields_match() directly
+ promisor-remote: try accepted remotes before others in get_direct()
(this branch is used by cc/promisor-auto-config-url-more.)
Promisor remote handling has been refactored and fixed in
preparation for auto-configuration of advertised remotes.
source: <20260407115243.358642-1-christian.couder@gmail•com>
* dl/cache-tree-fully-valid-fix (2026-04-06) 1 commit
(merged to 'next' on 2026-04-13 at 68c82a9f37)
+ cache-tree: fix inverted object existence check in cache_tree_fully_valid
The check that implements the logic to see if an in-core cache-tree
is fully ready to write out a tree object was broken, which has
been corrected.
source: <20260406192711.68870-1-davidlin@stripe•com>
* ja/doc-difftool-synopsis-style (2026-04-04) 4 commits
(merged to 'next' on 2026-04-13 at 0e6c98f313)
+ doc: convert git-describe manual page to synopsis style
+ doc: convert git-shortlog manual page to synopsis style
+ doc: convert git-range-diff manual page to synopsis style
+ doc: convert git-difftool manual page to synopsis style
Doc mark-up updates.
source: <pull.2077.git.1775322767.gitgitgadget@gmail•com>
* jc/doc-timestamps-in-stat (2026-04-10) 1 commit
(merged to 'next' on 2026-04-20 at 0680260012)
+ CodingGuidelines: st_mtimespec vs st_mtim vs st_mtime
Doc update.
source: <xmqqzf3aofdj.fsf_-_@gitster•g>
* ps/test-set-e-clean (2026-04-21) 12 commits
(merged to 'next' on 2026-04-23 at 4f69b47b94)
+ t: detect errors outside of test cases
+ t9902: fix use of `read` with `set -e`
+ t6002: fix use of `expr` with `set -e`
+ t1301: don't fail in case setfacl(1) doesn't exist or fails
+ t0008: silence error in subshell when using `grep -v`
+ t: prepare `test_when_finished ()`/`test_atexit()` for `set -e`
+ t: prepare execution of potentially failing commands for `set -e`
+ t: prepare conditional test execution for `set -e`
+ t: prepare `git config --unset` calls for `set -e`
+ t: prepare `stop_git_daemon ()` for `set -e`
+ t: prepare `test_must_fail ()` for `set -e`
+ t: prepare `test_match_signal ()` calls for `set -e`
The test suite harness and many individual test scripts have been
updated to work correctly when 'set -e' is in effect, which helps
detect misspelled test commands.
source: <20260421-b4-pks-tests-with-set-e-v6-0-26330e3061ab@pks•im>
* sb/userdiff-lisp-family (2026-04-14) 2 commits
(merged to 'next' on 2026-04-20 at 5897c04899)
+ userdiff: extend Scheme support to cover other Lisp dialects
+ userdiff: tighten word-diff test case of the scheme driver
The userdiff driver for the Scheme language has been extended to
cover other Lisp dialects.
source: <pull.2000.v4.git.1776220063.gitgitgadget@gmail•com>
* sp/refs-reduce-the-repository (2026-04-04) 3 commits
(merged to 'next' on 2026-04-09 at bb1d626802)
+ refs/reftable-backend: drop uses of the_repository
+ refs: remove the_hash_algo global state
+ refs: add struct repository parameter in get_files_ref_lock_timeout_ms()
Code clean-up to use the right instance of a repository instance in
calls inside refs subsystem.
source: <20260404135914.61195-1-shreyanshpaliwalcmsmn@gmail•com>
--------------------------------------------------
[New Topics]
* js/mingw-no-nedmalloc (2026-05-08) 3 commits
- mingw: remove the vendored compat/nedmalloc/ subtree
- mingw: drop the build-system plumbing for nedmalloc
- mingw: stop using nedmalloc
Stop using unmaintained custom allocator in Windows build which was
the last user of the code.
Will merge to 'next'.
source: <pull.2104.v3.git.1778244661.gitgitgadget@gmail•com>
* sj/submodule-update-clone-config-fix (2026-05-09) 1 commit
- submodule-config: fix reading submodule.fetchJobs
The configuration variable submodule.fetchJobs was not read correctly,
which has been corrected.
Will merge to 'next'.
source: <pull.2287.v4.git.git.1778385022964.gitgitgadget@gmail•com>
* aw/validate-proxy-url-scheme (2026-05-05) 1 commit
- http: reject unsupported proxy URL schemes
Misspelt proxy URL (e.g., httt://...) did not trigger any warning
or failure, which has been corrected.
Will merge to 'next'?
source: <20260505091941.1825-2-aminnimaj@gmail•com>
* hn/branch-prune-merged (2026-05-05) 6 commits
- branch: add --all-remotes flag
- branch: add branch.<name>.pruneMerged opt-out
- fetch: add --prune-merged
- branch: add --prune-merged <remote>
- branch: let delete_branches warn instead of error on bulk refusal
- branch: add --forked <remote>
"git branch" command learned "--prune-merged" option to remove
local branches that have already been merged to the remote-tracking
branches they track.
Expecting a reroll to remove "fetch" part?
cf. <20260505220712.93952-1-haraldnordgren@gmail•com>
source: <pull.2285.v4.git.git.1778009038.gitgitgadget@gmail•com>
* kh/doc-restore-double-underscores-fix (2026-05-05) 1 commit
- doc: restore: remove double underscore
Doc update.
Will merge to 'next'.
source: <double_underscore.670@msgid•xyz>
* mm/diff-U-takes-no-negative-values (2026-05-05) 3 commits
- xdiff: guard against negative context lengths
- diff: reject negative values for -U/--unified
- diff: reject negative values for --inter-hunk-context
The command line parser for "git diff" learned a few options take
only non-negative integers.
Will merge to 'next'?
source: <pull.2105.git.1778022144.gitgitgadget@gmail•com>
* ps/clang-w-glibc-2.43-and-_Generic (2026-05-05) 1 commit
- build: tolerate use of _Generic from glibc 2.43 with Clang
Headers from glibc 2.43 when used with clang does not allow
disabling C11 language features, causing build failures..
Will merge to 'next'.
source: <20260505-b4-pks-ci-tolerate-glibc-generic-v1-1-5786386fe512@pks•im>
* mm/git-url-parse (2026-05-01) 8 commits
- t9904: add tests for the new url-parse builtin
- doc: describe the url-parse builtin
- builtin: create url-parse command
- urlmatch: define url_parse function
- url: return URL_SCHEME_UNKNOWN instead of dying
- url: move scheme detection to URL header/source
- url: move url_is_local_not_ssh to url.h
- connect: rename enum protocol to url_scheme
The internal URL parsing logic has been made accessible via a new
subcommand "git url-parse".
Will merge to 'next'?
source: <pull.1715.v3.git.git.1777699722.gitgitgadget@gmail•com>
* kh/doc-commit-graph (2026-05-07) 1 commit
- doc: add caveat about turning off commit-graph
Ramifications of turning off commit-graph has been documented a bit
more clearly.
source: <V3_caveat_commit-graph.6b6@msgid•xyz>
* dk/doc-exclude-is-shared-per-repo (2026-05-08) 1 commit
- ignore: note info/exclude lives in GIT_COMMON_DIR, not GIT_DIR
Document the fact that .git/info/exclude is shared across worktrees
linked to the same repository.
Will merge to 'next'?
source: <d58b6e921d3005c6170fc6c47f175214acb3fa68.1778249267.git.ben.knoble+github@gmail•com>
* jc/t5551-fix-expensive (2026-05-07) 1 commit
- t5551: "GIT_TEST_LONG=Yes make test" is broken
Test fix.
Will merge to 'next'.
source: <xmqqqznmeaco.fsf@gitster•g>
* kk/paint-down-to-common-optim (2026-05-08) 1 commit
- commit-reach: early exit paint_down_to_common for single merge-base
"git merge-base" optimization.
Comments?
source: <pull.2109.git.1778252837132.gitgitgadget@gmail•com>
* st/daemon-sockaddr-fixes (2026-05-08) 1 commit
- daemon: fix network address handling bugs
Correct use of sockaddr API in "git daemon".
Comments?
source: <pull.2299.git.git.1778291290159.gitgitgadget@gmail•com>
* ag/rebase-update-refs-limit-to-branches (2026-05-10) 1 commit
- rebase: ignore non-branch update-refs
"git rebase --update-refs", when used with an rebase.instructionFormat
with "%d" (describe) in it, tried to update local branch HEAD by
mistake, which has been corrected.
Will merge to 'next'.
source: <20260510224111.64467-2-mail@abhinavg•net>
* jc/ci-enable-expensive (2026-05-10) 2 commits
- ci: enable EXPENSIVE for contributor builds
- Merge branch 'js/objects-larger-than-4gb-on-windows' into jc/ci-enable-expensive
(this branch uses js/objects-larger-than-4gb-on-windows.)
Enable expensive tests to catch topics that may cause breakages on
integration branches closer to their origin in the contributor PR
builds.
Comments?
source: <xmqqjyta9630.fsf@gitster•g>
* rs/sideband-clear-line-before-print (2026-05-10) 1 commit
- sideband: clear full line when printing remote messages
Tweak the way how sideband messages from remote are printed while
we talk with a remote repository to avoid tickling terminal
emulator glitches.
Will merge to 'next'.
source: <9826dabf-c9a6-4397-8ae6-a24f9c507f1b@web•de>
--------------------------------------------------
[Cooking]
* jh/alias-i18n-fixes (2026-04-24) 1 commit
- alias: restore support for simple dotted aliases
Further update to the i18n alias support to avoid regressions.
Will merge to 'next'?
source: <20260424161707.1514255-1-jonatan@jontes•page>
* kn/refs-generic-helpers (2026-05-04) 9 commits
- refs: use peeled tag values in reference backends
- refs: add peeled object ID to the `ref_update` struct
- refs: move object parsing to the generic layer
- update-ref: handle rejections while adding updates
- update-ref: move `print_rejected_refs()` up
- refs: return `ref_transaction_error` from `ref_transaction_update()`
- refs: extract out reflog config to generic layer
- refs: introduce `ref_store_init_options`
- refs: remove unused typedef 'ref_transaction_commit_fn'
Refactor service routines in the ref subsystem backends.
Will merge to 'next'?
source: <20260504-refs-move-to-generic-layer-v4-0-936ac2f0b1a3@gmail•com>
* ob/more-repo-config-values (2026-04-23) 8 commits
- env: move "warn_on_object_refname_ambiguity" into `struct repo_config_values`
- env: move "sparse_expect_files_outside_of_patterns" into `repo_config_values`
- env: move "core_sparse_checkout_cone" into `struct repo_config_values`
- environment: move "precomposed_unicode" into `struct repo_config_values`
- environment: move "pack_compression_level" into `struct repo_config_values`
- environment: move `zlib_compression_level` into `struct repo_config_values`
- environment: move "check_stat" into `struct repo_config_values`
- environment: move "trust_ctime" into `struct repo_config_values`
Expecting a reroll.
cf. <CAD=f0L8-_3sDGGkCzF4WA0xmUtaY_qiz__3zq5AemLgwTsqvsg@mail•gmail.com>
source: <20260423165432.143598-1-belkid98@gmail•com>
* ps/history-fixup (2026-04-26) 3 commits
- builtin/history: introduce "fixup" subcommand
- builtin/history: generalize function to commit trees
- replay: allow callers to control what happens with empty commits
"git history" learned "fixup" command.
Comments?
source: <20260427-b4-pks-history-fixup-v3-0-cb908f06264b@pks•im>
* rs/grep-column-only-match-fix (2026-04-24) 1 commit
- grep: fix --column --only-match for 2nd and later matches
"git grep" update.
Will merge to 'next'.
source: <9bd69678-f04b-41d2-ad74-a386820d34c8@web•de>
* sb/unpack-index-pack-buffer-resize (2026-04-28) 1 commit
- index-pack, unpack-objects: increase input buffer from 4 KiB to 128 KiB
Use a larger buffer size in the code paths to ingest pack stream.
Will merge to 'next'?
source: <pull.2282.v4.git.git.1777387660841.gitgitgadget@gmail•com>
* bc/sign-commit-with-custom-encoding (2026-04-27) 2 commits
- commit: sign commit after mutating buffer
- commit: name UTF-8 function appropriately
Signing commit with custom encoding was passing the data to be
signed at a wrong stage in the pipeline, which has been corrected.
Will merge to 'next'?
source: <20260427221834.1824543-1-sandals@crustytoothpaste•net>
* cc/promisor-auto-config-url-more (2026-04-27) 9 commits
- doc: promisor: improve acceptFromServer entry
- promisor-remote: auto-configure unknown remotes
- promisor-remote: trust known remotes matching acceptFromServerUrl
- promisor-remote: introduce promisor.acceptFromServerUrl
- promisor-remote: add 'local_name' to 'struct promisor_info'
- urlmatch: add url_normalize_pattern() helper
- urlmatch: change 'allow_globs' arg to bool
- t5710: simplify 'mkdir X' followed by 'git -C X init'
- Merge branch 'cc/promisor-auto-config-url' into cc/promisor-auto-config-url-more
The handling of promisor-remote protocol capability has been
loosened to allow the other side to add to the list of promisor
remotes via the promisor.acceptFromServerURL configuration
variable.
Comments?
cf. <875x4yoys5.fsf@toon--20250203-5JQV3•mail-host-address-is-not-set>
source: <20260427124108.3524129-1-christian.couder@gmail•com>
* js/maintenance-fix-deadlock-on-win10 (2026-05-07) 2 commits
- maintenance(geometric): do release the `.idx` files before repacking
- mingw: optionally use legacy (non-POSIX) delete semantics
To help Windows 10 installations, avoid removing files whose
contents are still mmap()'ed.
Will merge to 'next'.
source: <pull.2103.v2.git.1778158273.gitgitgadget@gmail•com>
* js/objects-larger-than-4gb-on-windows (2026-05-08) 11 commits
- ci: run expensive tests on push builds to integration branches
- t5608: mark >4GB tests as EXPENSIVE
- test-tool synthesize: add precomputed SHA-256 pack for 4 GiB + 1
- test-tool synthesize: precompute pack for 4 GiB + 1
- test-tool synthesize: use the unsafe hash for speed
- t5608: add regression test for >4GB object clone
- test-tool: add a helper to synthesize large packfiles
- delta, packfile: use size_t for delta header sizes
- odb, packfile: use size_t for streaming object sizes
- git-zlib: handle data streams larger than 4GB
- index-pack, unpack-objects: use size_t for object size
(this branch is used by jc/ci-enable-expensive.)
Update code paths that assumed "unsigned long" was long enough for
"size_t".
Will merge to 'next'.
source: <pull.2102.v3.git.1778228209.gitgitgadget@gmail•com>
* js/t5564-socks-use-short-path (2026-04-29) 1 commit
(merged to 'next' on 2026-05-11 at fbb23860ca)
+ t5564: use a short path for the SOCKS proxy socket
Avoid hitting the pathname limit for socks proxy socket during the
test..
Will merge to 'master'.
source: <pull.2100.v2.git.1777450974159.gitgitgadget@gmail•com>
* kh/doc-log-decorate-list (2026-04-27) 2 commits
- doc: log: use the same delimiter in description list
- doc: log: fix --decorate description list
Doc update.
Comments?
source: <CV_doc_log_--decorate_list.626@msgid•xyz>
* za/t2000-modernise-more (2026-04-29) 1 commit
- t2000: consolidate second scenario into a single test block
Test update.
Comments?
source: <20260429103607.406339-1-zakariyahali100@gmail•com>
* hn/checkout-track-fetch (2026-05-08) 1 commit
- checkout: extend --track with a "fetch" mode to refresh start-point
"git checkout --track=..." learned to optionally fetch the branch
from the remote the new branch will work with.
Comments?
cf. <f23eb128-958f-475f-911b-eac4f6daddff@gmail•com>
source: <pull.2281.v7.git.git.1778280727849.gitgitgadget@gmail•com>
* mf/revision-max-count-oldest (2026-05-09) 2 commits
- SQUASH??? tac is not portable
- revision.c: implement --max-count-oldest
"git rev-list" (and "git log" family of commands) learned a new "--max-count-oldest"
that picks oldest N commits in the range instead of the usual newest.
Comments?
source: <2f71a00b035e25b971641b77a6fa7626f1e2459c.1777578676.git.mroik@delayed•space>
* mm/line-log-cleanup (2026-04-27) 3 commits
- line-log: allow non-patch diff formats with -L
- line-log: integrate -L output with the standard log-tree pipeline
- revision: move -L setup before output_format-to-diff derivation
Code clean-up.
Comments?
source: <pull.2094.git.1777349126.gitgitgadget@gmail•com>
* pw/rename-to-get-current-worktree (2026-05-01) 1 commit
- worktree: rename get_worktree_from_repository()
Code clean-up.
Will merge to 'next'.
source: <bd48396137f8d1352d11b3bd2dca2848f24a347d.1777648798.git.phillip.wood@dunelm•org.uk>
* ds/path-walk-filters (2026-05-04) 11 commits
- path-walk: support `combine` filter
- path-walk: support `object:type` filter
- path-walk: support `tree:0` filter
- pack-objects: support sparse:oid filter with path-walk
- path-walk: add pl_sparse_trees to control tree pruning
- path-walk: support blob size limit filter
- backfill: die on incompatible filter options
- path-walk: support blobless filter
- t/perf: add pack-objects filter and path-walk benchmark
- pack-objects: pass --objects with --path-walk
- Merge branch 'en/backfill-fixes-and-edges' into ds/path-walk-filters
(this branch uses en/backfill-fixes-and-edges.)
The "git pack-objects --path-walk" traversal has been integrated
with several object filters, including blobless and sparse filters.
Expecting a reroll?
cf. <07b36bd8-376b-4a98-a735-0c0f75452c24@gmail•com>
source: <pull.2101.v2.git.1777926079.gitgitgadget@gmail•com>
* en/ort-cached-rename-with-trivial-resolution (2026-04-20) 1 commit
(merged to 'next' on 2026-05-11 at 9fe24668d9)
+ merge-ort: handle cached rename & trivial resolution interaction better
"ort" merge backend improvements.
Will merge to 'master'.
source: <pull.2095.git.1776724214171.gitgitgadget@gmail•com>
* en/ort-harden-against-corrupt-trees (2026-04-20) 5 commits
- cache-tree: fix verify_cache() to catch non-adjacent D/F conflicts
- merge-ort: abort merge when trees have duplicate entries
- merge-ort: free diff pairs queue in clear_or_reinit_internal_opts()
- merge-ort: drop unnecessary show_all_errors from collect_merge_info()
- merge-ort: propagate callback errors from traverse_trees_wrapper()
"ort" merge backend handles merging corrupt trees better by
aborting when it should.
Needs review.
source: <pull.2096.git.1776731171.gitgitgadget@gmail•com>
* jk/revert-aa-reap-transport-child-processes (2026-04-22) 1 commit
(merged to 'next' on 2026-05-11 at b41904c1d3)
+ Revert "transport-helper, connect: use clean_on_exit to reap children on abnormal exit"
Revert a recent change that introduced a regression to help mksh users.
Will merge to 'master'.
source: <20260422230020.GA1839627@coredump•intra.peff.net>
* js/ci-github-actions-update (2026-04-30) 6 commits
(merged to 'next' on 2026-05-11 at ba87f84054)
+ l10n: bump mshick/add-pr-comment from v2 to v3
+ ci: bump git-for-windows/setup-git-for-windows-sdk from v1 to v2
+ ci: bump actions/checkout from v5 to v6
+ ci: bump actions/github-script from v8 to v9
+ ci: bump actions/{upload,download}-artifact to v7 and v8
+ ci: bump microsoft/setup-msbuild from v2 to v3
Update various GitHub Actions versions.
Will merge to 'master'.
source: <pull.2097.v3.git.1777534500.gitgitgadget@gmail•com>
* mf/format-patch-cover-letter-format-docfix (2026-04-22) 1 commit
(merged to 'next' on 2026-05-11 at 3cca9cc117)
+ Fix docs for format.commitListFormat
Docfix.
Will merge to 'master'.
source: <576d29f15e016889e02c253713656cd8cbf1f04c.1776894255.git.mroik@delayed•space>
* sg/t6112-unwanted-tilde-expansion-fix (2026-04-21) 1 commit
- t6112: avoid tilde expansion
Test fix.
Will merge to 'next'.
source: <20260421192132.51172-1-szeder.dev@gmail•com>
* pw/status-rebase-todo (2026-05-01) 2 commits
- status: improve rebase todo list parsing
- sequencer: factor out parsing of todo commands
The display of the rebase todo list in "git status" has been
improved to correctly abbreviate object IDs for more commands and
avoid misinterpreting refs as object IDs.
Needs review.
source: <cover.1777648598.git.phillip.wood@dunelm•org.uk>
* ss/t7004-unhide-git-failures (2026-04-20) 3 commits
(merged to 'next' on 2026-05-11 at 9ee9feacb7)
+ t7004: avoid subshells to capture git exit codes
+ t7004: dynamically grab expected state in tests
+ t7004: drop hardcoded tag count for state verification
Test clean-up.
Will merge to 'master'.
cf. <aecNc-BNwaqFlg5c@pks•im>
source: <20260421053334.5414-1-r.siddharth.shrimali@gmail•com>
* tb/pseudo-merge-bugfixes (2026-04-21) 9 commits
- pack-bitmap: prevent pattern leak on pseudo-merge re-assignment
- Documentation: fix broken `sampleRate` in gitpacking(7)
- pack-bitmap: reject pseudo-merge "sampleRate" of 0
- pack-bitmap: parse commits in `find_pseudo_merge_group_for_ref()`
- pack-bitmap: fix pseudo-merge lookup for shared commits
- pack-bitmap: fix inverted binary search in `pseudo_merge_at()`
- pack-bitmap-write: sort pseudo-merge commit lookup table in pack order
- t5333: demonstrate various pseudo-merge bugs
- t/helper: add 'test-tool bitmap write' subcommand
Fixes many bugs in pseudo-merge code.
Expecting (hopefully minor and final) reroll.
cf. <CABPp-BGkfavqezk2SV3+K6iF8MLm8j_=ijHiPDLmv_U_o_Ykgg@mail•gmail.com>
source: <cover.1776801694.git.me@ttaylorr•com>
* ds/fetch-negotiation-options (2026-04-22) 7 commits
- send-pack: pass negotiation config in push
- remote: add remote.*.negotiationInclude config
- fetch: add --negotiation-include option for negotiation
- remote: add remote.*.negotiationRestrict config
- transport: rename negotiation_tips
- fetch: add --negotiation-restrict option
- t5516: fix test order flakiness
The negotiation tip options in "git fetch" have been reworked to
allow requiring certain refs to be sent as "have" lines, and to
restrict negotiation to a specific set of refs.
Needs review.
source: <pull.2085.v3.git.1776871546.gitgitgadget@gmail•com>
* en/backfill-fixes-and-edges (2026-04-15) 3 commits
(merged to 'next' on 2026-05-11 at baccbdf26d)
+ backfill: default to grabbing edge blobs too
+ backfill: document acceptance of revision-range in more standard manner
+ backfill: reject rev-list arguments that do not make sense
(this branch is used by ds/path-walk-filters.)
The 'git backfill' command now rejects revision-limiting options that
are incompatible with its operation, uses standard documentation for
revision ranges, and includes blobs from boundary commits by default
to improve performance of subsequent operations.
Will merge to 'master'.
cf. <6e95b82a-19e3-460e-86f7-f899c2df261d@gmail•com>
source: <pull.2088.git.1776297482.gitgitgadget@gmail•com>
* mc/http-emptyauth-negotiate-fix (2026-04-30) 4 commits
- doc: clarify http.emptyAuth values
(merged to 'next' on 2026-04-20 at 6539524ca2)
+ t5563: add tests for http.emptyAuth with Negotiate
+ http: attempt Negotiate auth in http.emptyAuth=auto mode
+ http: extract http_reauth_prepare() from retry paths
The 'http.emptyAuth=auto' configuration now correctly attempts
Negotiate authentication before falling back to manual credentials.
This allows seamless Kerberos ticket-based authentication without
requiring users to explicitly set 'http.emptyAuth=true'.
Will merge to 'next' and then to 'master'.
source: <e0f236767f81ea60f90749d1bc00ab78081efd0e.1777546472.git.gitgitgadget@gmail•com>
source: <pull.2087.git.1776331259.gitgitgadget@gmail•com>
* en/batch-prefetch (2026-04-17) 3 commits
- grep: prefetch necessary blobs
- builtin/log: prefetch necessary blobs for `git cherry`
- patch-ids.h: add missing trailing parenthesis in documentation comment
In a lazy clone, "git cherry" and "git grep" often fetch necessary
blob objects one by one from promisor remotes. It has been corrected
to collect necessary object names and fetch them in bulk to gain
reasonable performance.
Needs review.
source: <pull.2089.v2.git.1776472347.gitgitgadget@gmail•com>
* en/diffstat-utf8-truncation-fix (2026-04-20) 1 commit
- diff: fix out-of-bounds reads and NULL deref in diffstat UTF-8 truncation
The computation to shorten the filenames shown in diffstat measured
width of individual UTF-8 characters to add up, but forgot to take
into account error cases (e.g., an invalid UTF-8 sequence, or a
control character).
Will merge to 'next'?
source: <pull.2093.v3.git.1776699778177.gitgitgadget@gmail•com>
* ps/odb-in-memory (2026-04-10) 18 commits
- t/unit-tests: add tests for the in-memory object source
- odb: generic in-memory source
- odb/source-inmemory: stub out remaining functions
- odb/source-inmemory: implement `freshen_object()` callback
- odb/source-inmemory: implement `count_objects()` callback
- odb/source-inmemory: implement `find_abbrev_len()` callback
- odb/source-inmemory: implement `for_each_object()` callback
- odb/source-inmemory: convert to use oidtree
- oidtree: add ability to store data
- cbtree: allow using arbitrary wrapper structures for nodes
- odb/source-inmemory: implement `write_object_stream()` callback
- odb/source-inmemory: implement `write_object()` callback
- odb/source-inmemory: implement `read_object_stream()` callback
- odb/source-inmemory: implement `read_object_info()` callback
- odb: fix unnecessary call to `find_cached_object()`
- odb/source-inmemory: implement `free()` callback
- odb: introduce "in-memory" source
- Merge branch 'jt/odb-transaction-write' into ps/odb-in-memory
(this branch uses jt/odb-transaction-write.)
Add a new odb "in-memory" source that is meant to only hold
tentative objects (like the virtual blob object that represents the
working tree file used by "git blame").
Will merge to 'next'.
source: <20260410-b4-pks-odb-source-inmemory-v3-0-22fd0fad58fe@pks•im>
* js/adjust-tests-to-explicitly-access-bare-repo (2026-04-26) 8 commits
- safe.bareRepository: default to "explicit" with WITH_BREAKING_CHANGES
- status tests: filter `.gitconfig` from status output
- ls-files tests: filter `.gitconfig` from `--others` output
- t5601: restore `.gitconfig` after includeIf test
- t1305: use `--git-dir=.` for bare repo in include cycle test
- t1300: remove global config settings injected by test-lib.sh
- t7900: do not let `$HOME/.gitconfig` interfere with XDG tests
- test-lib: allow bare repository access when breaking changes are enabled
Some tests assume that bare repository accesses are by default
allowed; rewrite some of them to avoid the assumption, rewrite
others to explicitly set safe.bareRepository to allow them.
Will merge to 'next'?
source: <pull.2098.v2.git.1777214316.gitgitgadget@gmail•com>
* cl/conditional-config-on-worktree-path (2026-04-03) 2 commits
- config: add "worktree" and "worktree/i" includeIf conditions
- config: refactor include_by_gitdir() into include_by_path()
The [includeIf "condition"] conditional inclusion facility for
configuration files has learned to use the location of worktree
in its condition.
Comments?
source: <20260403-includeif-worktree-v3-0-109ce5782b03@black-desk•cn>
* ps/shift-root-in-graph (2026-04-27) 1 commit
- graph: add indentation for commits preceded by a parentless commit
In a history with more than one root commit, "git log --graph
--oneline" stuffed an unrelated commit immediately below a root
commit, which has been corrected by making the spot below a root
unavailable.
Will merge to 'next'?
source: <20260427102838.44867-2-pabloosabaterr@gmail•com>
* jt/config-lock-timeout (2026-04-03) 1 commit
- config: retry acquiring config.lock for 100ms
The code path to update the configuration file has been taught to
use a short timeout to retry.
Waiting for a review response.
cf. <adYvSZeN0ZVqwRhi@pks•im>
source: <20260403100135.3901610-1-joerg@thalheim•io>
* lp/repack-propagate-promisor-debugging-info (2026-04-18) 6 commits
- repack-promisor: add missing headers
- t7703: test for promisor file content after geometric repack
- t7700: test for promisor file content after repack
- repack-promisor: preserve content of promisor files after repack
- repack-promisor add helper to fill promisor file after repack
- pack-write: add explanation to promisor file content
When fetching objects into a lazily cloned repository, .promisor
files are created with information meant to help debugging. "git
repack" has been taught to carry this information forward to
packfiles that are newly created.
Comments?
source: <cover.1776384902.git.lorenzo.pegorari2002@gmail•com>
* th/promisor-quiet-per-repo (2026-04-06) 1 commit
- promisor-remote: fix promisor.quiet to use the correct repository
The "promisor.quiet" configuration variable was not used from
relevant submodules when commands like "grep --recurse-submodules"
triggered a lazy fetch, which has been corrected.
Comments?
source: <20260406183041.783800-1-vikingtc4@gmail•com>
* jt/odb-transaction-write (2026-04-02) 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
(this branch is used by ps/odb-in-memory.)
ODB transaction interface is being reworked to explicitly handle
object writes.
Will merge to 'next'.
source: <20260402213220.2651523-1-jltobler@gmail•com>
* sa/cat-file-batch-mailmap-switch (2026-04-15) 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: <20260416033250.4327-2-siddharthasthana31@gmail•com>
* tb/incremental-midx-part-3.3 (2026-04-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 `--no-write-chain-file` for incremental MIDX writes
- midx: use `strvec` for `keep_hashes`
- midx: build `keep_hashes` array in order
- midx: use `strset` 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.
Will merge to 'next'?
source: <cover.1777507303.git.me@ttaylorr•com>
* 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.
Comments?
source: <pull.2258.v2.git.git.1774971267.gitgitgadget@gmail•com>
* ps/setup-wo-the-repository (2026-04-20) 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: <20260420-pks-setup-wo-the-repository-v1-0-f4a81c4988e8@pks•im>
* kh/doc-trailers (2026-04-13) 9 commits
- doc: interpret-trailers: document comment line treatment
- doc: interpret-trailers: commit to “trailer block” term
- doc: interpret-trailers: add key format example
- doc: interpret-trailers: explain key format
- doc: interpret-trailers: explain the format after the intro
- doc: interpret-trailers: not just for commit messages
- doc: interpret-trailers: use “metadata” in Name as well
- doc: interpret-trailers: replace “lines” with “metadata”
- doc: interpret-trailers: stop fixating on RFC 822
Documentation updates.
Needs review.
source: <V2_CV_doc_int-tr_key_format.613@msgid•xyz>
* 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. <bdff0a5d-b738-4053-9b72-08eba88156de@kdbg•org>
source: <20260328001113.1275291-1-pabloosabaterr@gmail•com>
* jr/bisect-custom-terms-in-output (2026-04-17) 2 commits
- rev-parse: use selected alternate terms to look up refs
- bisect: use selected alternate terms in status output
"git bisect" now uses the selected terms (e.g., old/new) more
consistently in its output.
Needs review.
source: <20260417-bisect-terms-v3-0-d659fa547261@schlaraffenlan•de>
* ua/push-remote-group (2026-05-03) 3 commits
- push: support pushing to a remote group
- remote: move remote group resolution to remote.c
- remote: fix sign-compare warnings in push_cas_option
"git push" learned to take a "remote group" name to push to, which
causes pushes to multiple places, just like "git fetch" would do.
Comments?
source: <20260503153402.1333220-1-usmanakinyemi202@gmail•com>
* hn/git-checkout-m-with-stash (2026-04-28) 5 commits
- checkout -m: autostash when switching branches
- checkout: rollback lock on early returns in merge_working_tree
- sequencer: teach autostash apply to take optional conflict marker labels
- sequencer: allow create_autostash to run silently
- stash: add --label-ours, --label-theirs, --label-base 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.
Will merge to 'next'.
source: <pull.2234.v16.git.git.1777401552.gitgitgadget@gmail•com>
* kh/name-rev-custom-format (2026-05-07) 5 commits
- format-rev: introduce builtin for on-demand pretty formatting
- name-rev: make dedicated --annotate-stdin --name-only test
- name-rev: factor code for sharing with a new command
- name-rev: run clang-format before factoring code
- name-rev: wrap both blocks in braces
A new builtin "git format-rev" is introduced for pretty formatting
one revision expression per line or commit object names found in
running text.
Will merge to 'next'.
source: <V4_CV_format-rev.6aa@msgid•xyz>
* js/parseopt-subcommand-autocorrection (2026-04-27) 11 commits
- SQUASH???
- 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 a reroll.
source: <SY0P300MB0801677A2A1E0FD38D06A841CE2A2@SY0P300MB0801•AUSP300.PROD.OUTLOOK.COM>
* 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. <abe1l8ONmFIhzaxi@pks•im>
source: <pull.2058.v6.git.1773553022381.gitgitgadget@gmail•com>
* 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: <20260305233452.3727126-1-gitster@pobox•com>
* 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: <20260305233452.3727126-8-gitster@pobox•com>
* 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: <20260305-cs-subtree-split-recursion-v2-0-7266be870ba9@howdoi•land>
* 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.
Will discard.
cf. <xmqqik9s6qvd.fsf@gitster•g>
source: <pull.2224.v3.git.git.1773238778894.gitgitgadget@gmail•com>
* pt/fsmonitor-linux (2026-04-15) 13 commits
- 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
- t9210, t9211: disable GIT_TEST_SPLIT_INDEX for scalar clone tests
The fsmonitor daemon has been implemented for Linux.
Will merge to 'next'?
source: <pull.2147.v15.git.git.1776259657.gitgitgadget@gmail•com>
* pw/xdiff-shrink-memory-consumption (2026-05-04) 5 commits
- xdiff: reduce the size of array
- xprepare: simplify error handling
- xdiff: cleanup xdl_clean_mmatch()
- xdiff: reduce size of action arrays
- Merge branch 'en/xdiff-cleanup-3' into pw/xdiff-shrink-memory-consumption
(this branch uses en/xdiff-cleanup-3.)
Shrink wasted memory in Myers diff that does not account for common
prefix and suffix removal.
Will merge to 'next'?
source: <cover.1777903579.git.phillip.wood@dunelm•org.uk>
* en/xdiff-cleanup-3 (2026-04-29) 6 commits
- xdiff/xdl_cleanup_records: make execution of action easier to follow
- 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
(this branch is used by pw/xdiff-shrink-memory-consumption.)
Preparation of the xdiff/ codebase to work with Rust.
Will merge to 'next'.
source: <pull.2156.v6.git.git.1777500495.gitgitgadget@gmail•com>
^ permalink raw reply [flat|nested] 9+ messages in thread* kh/name-rev-custom-format
2026-05-11 3:08 What's cooking in git.git (May 2026, #02) Junio C Hamano
@ 2026-05-11 13:22 ` Kristoffer Haugsbakk
0 siblings, 0 replies; 9+ messages in thread
From: Kristoffer Haugsbakk @ 2026-05-11 13:22 UTC (permalink / raw)
To: Junio C Hamano, git
On Mon, May 11, 2026, at 05:08, Junio C Hamano wrote:
> * kh/name-rev-custom-format (2026-05-07) 5 commits
> - format-rev: introduce builtin for on-demand pretty formatting
> - name-rev: make dedicated --annotate-stdin --name-only test
> - name-rev: factor code for sharing with a new command
> - name-rev: run clang-format before factoring code
> - name-rev: wrap both blocks in braces
>
> A new builtin "git format-rev" is introduced for pretty formatting
> one revision expression per line or commit object names found in
> running text.
>
> Will merge to 'next'.
> source: <V4_CV_format-rev.6aa@msgid•xyz>
I’m very glad that it ready for `next`. But... please hold off on
merging it to `next` for the next version. I managed to make an
AsciiDoc mistake.
Sorry about that.
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2026-05-11 13:22 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-25 4:20 What's cooking in git.git (Mar 2026, #10) Junio C Hamano
2026-03-25 6:13 ` Jeff King
2026-03-25 8:33 ` Shreyansh Paliwal
2026-03-25 19:50 ` Junio C Hamano
2026-03-26 18:07 ` kh/name-rev-custom-format Kristoffer Haugsbakk
2026-03-26 18:48 ` kh/name-rev-custom-format Junio C Hamano
2026-03-26 19:22 ` kh/name-rev-custom-format Kristoffer Haugsbakk
2026-03-26 19:44 ` kh/name-rev-custom-format Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2026-05-11 3:08 What's cooking in git.git (May 2026, #02) Junio C Hamano
2026-05-11 13:22 ` kh/name-rev-custom-format Kristoffer Haugsbakk
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox