What's cooking in git.git (Jul 2026, #12)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]




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. They 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, it can be resubmitted when new interest
arises).
The seventh batch of topics have now graduated to the 'master' branch.
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/
--------------------------------------------------
[New Topics]
* jc/remote-insteadof-leakfix (2026年07月25日) 1 commit
 - remote: plug memory leaks
 rewrites_release() in 'remote.c' has been updated to free 'struct
 rewrite' instances and their '.instead_of' arrays, and their contents.
 Will merge to 'next'.
 cf. <20260725161819.GA2343104@xxxxxxxxxxxxxxxxxxxxxxx>
 source: <xmqqpl0b12gj.fsf@gitster.g>
* tb/pack-with-duplicates (2026年07月24日) 5 commits
 - pack-bitmap: handle duplicate pack entries during MIDX reuse
 - test-tool bitmap: reject packs with duplicate objects
 - midx: verify duplicate pack entries by OID and offset
 - packfile: recover delta cycles through duplicate entries
 - t5308: test reverse indexes with duplicate objects
 The handling of packfiles with duplicate object entries has been
 hardened. Specifically, reverse index lookup, delta cycle
 recovery, multi-pack-index verification, and pack reuse paths have
 been updated to correctly handle or gracefully reject duplicate
 entries.
 Needs review.
 cf. <xmqqecgs3vg6.fsf@gitster.g>
 source: <cover.1784927134.git.ttaylorr@xxxxxxxxxx>
* ps/cat-file-remote-object-info-type (2026年07月25日) 6 commits
 - cat-file: unify default format
 - serve: advertise type capability
 - fetch-object-info: request all supported options dynamically
 - fetch-object-info: parse type from server response
 - protocol-caps: add type support to object-info
 - Merge branch 'ps/cat-file-remote-object-info' into ps/cat-file-remote-object-info-type
 (this branch uses ps/cat-file-remote-object-info.)
 The 'remote-object-info' command for 'git cat-file --batch-command'
 has been extended to support the '%(objecttype)' placeholder.
 Needs review.
 source: <20260725-objecttype-support-v1-0-2d4ca3bbabf1@xxxxxxxxx>
* rs/branch-delete-bisect-warning (2026年07月25日) 1 commit
 - branch: report active bisect run when rejecting delete
 'git branch -d' learned to report when a branch cannot be deleted
 because it is being used in an active bisect run.
 Will merge to 'next'?
 cf. <xmqqbjbtyd80.fsf@gitster.g>
 source: <590382fb-731b-4e14-911e-ff68356d1082@xxxxxx>
* jk/ci-static-analysis-image-bump (2026年07月26日) 2 commits
 - ci: bump ubuntu image version for static-analysis job
 - bloom: silence CHECK_ASSERTION_SIDE_EFFECTS false positive
 The image version used by the static-analysis CI job has been bumped
 to ubuntu-latest (Ubuntu 24.04), which brings in a newer Coccinelle
 version that resolves a severe performance regression. A false
 positive warning from the CHECK_ASSERTION_SIDE_EFFECTS build with
 GCC 15 in the Bloom filter code has also been silenced to facilitate
 the image upgrade.
 Will merge to 'next'?
 cf. <xmqqo6ftvhed.fsf@gitster.g>
 source: <20260726083254.GA3528497@xxxxxxxxxxxxxxxxxxxxxxx>
* jk/diff-relative-cached-unmerged-more (2026年07月26日) 3 commits
 - diff-lib: skip paths outside prefix in oneway_diff()
 - diff-lib: drop stale comment about advancing o->pos
 - Merge branch 'jk/diff-relative-cached-unmerged' into jk/diff-relative-cached-unmerged-more
 (this branch uses jk/diff-relative-cached-unmerged.)
 The code path that deals with relative paths in the diff-lib has
 been cleaned up.
 Will merge to 'next'?
 cf. <xmqqjyqhv7s7.fsf@gitster.g>
 source: <20260726084550.GC2366012@xxxxxxxxxxxxxxxxxxxxxxx>
--------------------------------------------------
[Stalled]
* tb/repack-geometric-cruft (2026年06月28日) 11 commits
 - SQUASH??? bare grep !???
 - repack: support combining '--geometric' with '--cruft'
 - pack-objects: support '--refs-snapshot' with 'follow-reachable'
 - pack-objects: introduce '--stdin-packs=follow-reachable'
 - pack-objects: extract `stdin_packs_add_all_pack_entries()`
 - repack-geometry: drop unused redundant-pack removal
 - repack: delete geometric packs via existing_packs
 - repack: teach MIDX retention about geometric rollups
 - repack: mark geometric progression of packs as retained
 - repack: extract `locate_existing_pack()` helper
 - repack: unconditionally exclude non-kept packs
 'git repack' has been taught to accept '--geometric' and '--cruft'
 together. When both are given, non-cruft packs are rolled up by the
 geometric repack as usual, while a separate cruft pack is written to
 collect unreachable objects.
 Waiting for response for too long, stalled.
 cf. <aj8cvDCMcw+RayyO@nand.local>
 cf. <aj8cOhH6hGVZIFft@nand.local>
 source: <cover.1782500507.git.me@xxxxxxxxxxxx>
* hn/checkout-track-fetch (2026年06月24日) 2 commits
 - checkout: extend --track with a "fetch" mode to refresh start-point
 - branch: expose helpers for finding the remote owning a tracking ref
 The 'git checkout --track=...' command has been taught to optionally
 fetch the branch from the remote that the new branch will work with.
 Will be discarded.
 cf. <xmqq5x37h6fj.fsf@gitster.g>
 cf. <CAL71e4MiijEiM26TKJcOYT7L4pfQeMM_F2oT3U3igP-wOZm2Ag@xxxxxxxxxxxxxx>
 cf. <xmqq8q71clob.fsf@gitster.g>
 source: <pull.2281.v15.git.git.1782338098.gitgitgadget@xxxxxxxxx>
* za/completion-hide-dotfiles (2026年06月20日) 2 commits
 - completion: hide dotfiles by default for path completion
 - completion: hide dotfiles for selected path completion
 Path completion for commands like 'git rm' and 'git mv' has been
 updated to hide dotfiles by default unless the user explicitly starts
 the path with a dot, matching standard shell-completion behavior.
 Waiting for response, stalled.
 cf. <xmqqbjd37i4y.fsf@gitster.g>
 cf. <xmqq4ihpclo8.fsf@gitster.g>
 source: <pull.2311.v3.git.git.1781978156.gitgitgadget@xxxxxxxxx>
* kh/doc-trailers (2026年06月10日) 10 commits
 - doc: interpret-trailers: document comment line treatment
 - doc: interpret-trailers: commit to “trailer block” term
 - doc: interpret-trailers: join new-trailers again
 - 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 for 'git interpret-trailers' has been updated to explain
 the format of trailer keys (alphanumeric characters and hyphens),
 replace outdated terminology, define key terms upfront, and document
 how comment lines in the input are treated.
 Expecting a reroll for too long, stalled.
 cf. <729baf6b-53ea-4e8d-95ab-5935667e66c2@xxxxxxxxxxxxxxxx>
 source: <V3_CV_doc_int-tr_key_format.8a3@xxxxxxxxx>
* kh/doc-replay-config (2026年06月05日) 4 commits
 - doc: replay: move “default” to the right-hand side
 - doc: replay: use a nested description list
 - doc: replay: improve config description
 - doc: link to config for git-replay(1)
 Documentation for 'git replay' has been updated to refer to its
 configuration variables.
 Waiting for response for too long, stalled.
 cf. <87cxwxofgv.fsf@xxxxxxxxxxxxxxx>
 cf. <xmqqv7a5b6n7.fsf@gitster.g>
 source: <V3_CV_doc_replay_config.780@xxxxxxxxx>
--------------------------------------------------
[Cooking]
* af/clone-revision-v0-segfault-fix (2026年07月24日) 1 commit
 - builtin/clone: fix segfault when using --revision with protocol v0
 'git clone --revision' talking to a server that does not support
 protocol v2 (falling back to protocol v0) segfaulted, which has
 been corrected.
 Will merge to 'next'.
 cf. <xmqqldb08jcd.fsf@gitster.g>
 source: <20260724124138.666877-1-adrian.friedli@xxxxxx>
* lo/mv-missing-dest-dir-check (2026年07月26日) 2 commits
 - mv: reject a destination whose leading path is missing or a symlink
 - mv: name both source and destination when rename fails
 'git mv' has been updated to check for a missing destination
 leading directory during the checking phase, allowing 'git mv -n'
 to report the failure. The error message when the rename(2)
 syscall fails has also been improved to name both the source and
 the destination.
 Needs review.
 source: <pull.2356.v4.git.git.1785097071.gitgitgadget@xxxxxxxxx>
* ps/odb-make-creation-pluggable (2026年07月23日) 5 commits
 - odb: make creation of on-disk structures pluggable
 - odb/source: introduce function to map source type to name
 - setup: defer object database creation
 - setup: detangle loading of loose object maps
 - loose: load loose object map for the correct source
 The creation of the on-disk data structures for the object database
 has been made pluggable, allowing future backends to customize their
 setup. As part of this, the initialization of the object database
 has been deferred, and the loading of the loose-object map has been
 detangled from repository initialization.
 Waiting for response.
 cf. <xmqq5x248fk9.fsf@gitster.g>
 cf. <xmqqh5lo6xi2.fsf@gitster.g>
 cf. <xmqq5x246x35.fsf@gitster.g>
 cf. <xmqqfr15v6ba.fsf@gitster.g>
 cf. <xmqqbjbtv5y6.fsf@gitster.g>
 source: <20260724-pks-odb-create-on-disk-v1-0-3b3d265d979b@xxxxxx>
* jt/config-lock-timeout (2026年05月17日) 1 commit
 (merged to 'next' on 2026年07月24日 at 3cb8da6b6a)
 + config: retry acquiring config.lock, configurable via core.configLockTimeout
 Configuration file locking has been updated to retry for a short
 period, avoiding failures when multiple processes attempt to update
 the configuration simultaneously.
 Will merge to 'master'.
 cf. <agrIrGwSMFlKTx9x@xxxxxx>
 cf. <xmqqzf1xbl4i.fsf@gitster.g>
 source: <20260517132111.1014901-1-joerg@xxxxxxxxxxx>
* hs/rebase-continue-edit (2026年07月21日) 1 commit
 - rebase: add --[no-]edit to --continue
 Support for skipping the editor when continuing a rebase after
 conflict resolution has been added with the '--no-edit' option, and
 forcing it with '--edit'. A new configuration variable
 'rebase.noEdit' can be used to set the default behavior.
 Waiting for a response.
 cf. <xmqqldb4xlqa.fsf@gitster.g>
 cf. <db7edc66-9b2a-47bc-98db-87d01885cef0@xxxxxxxxx>
 source: <20260721140443.1809379-2-hugo@xxxxxxx>
* tn/stash-avoid-sparse-index-expansion (2026年07月20日) 2 commits
 (merged to 'next' on 2026年07月23日 at 8ccf28493e)
 + stash: avoid sparse-index expansion for in-cone paths
 + pathspec: use match for sparse-index expansion checks
 The 'git stash push' command has been optimized to avoid unnecessary
 sparse index expansion when pathspecs are wholly inside the
 sparse-checkout cone. Also, a potential out-of-bounds read in the
 sparse-index expansion check helper pathspec_needs_expanded_index()
 has been fixed by consistently using the parsed, prefixed path.
 Will merge to 'master'.
 cf. <al61UTM0aK9j9eiP@com-79390>
 cf. <al61ERa3fS2MerHp@com-79390>
 source: <20260720223118.62821-4-tnyman@xxxxxxxxxx>
* en/submodule-insteadof-remote-match (2026年07月22日) 1 commit
 - submodule: resolve insteadOf aliases when matching remote
 The remote-matching logic for submodules has been corrected to
 resolve 'url.*.insteadOf' aliases before comparing the inventoried
 URL from '.gitmodules' with the URLs of configured remotes.
 Will merge to 'next'.
 cf. <xmqqldb05dlo.fsf@gitster.g>
 source: <20260723002132.3989727-1-ccjmne@xxxxxxxxx>
* td/fsmonitor-darwin-cookie-flush (2026年07月21日) 1 commit
 - fsmonitor: flush pending FSEvents before cookie wait
 The 'fsmonitor' daemon on macOS has been updated to flush pending
 FSEvents before waiting for the cookie file, to avoid premature
 timeouts on busy systems.
 Waiting for response.
 cf. <CAOTNsDy4pKbPHdK1T688Ax6Mgz15K-qfZR-8fAvTk48z3E43Rg@xxxxxxxxxxxxxx>
 cf. <xmqqh5lo5dib.fsf@gitster.g>
 source: <20260721-fsmonitor-darwin-cookie-flush-v1-1-357dc5e32040@xxxxxxxxx>
* jc/exclude-first-parent-seen (2026年07月22日) 1 commit
 (merged to 'next' on 2026年07月25日 at 85755d1d45)
 + revision: honor --exclude-first-parent-only with SEEN first parent
 Traversals with '--exclude-first-parent-only' have been corrected to
 properly stop after the first parent even when it has already been
 marked as SEEN.
 Will merge to 'master'.
 source: <xmqqbjbzq7n2.fsf@gitster.g>
* sn/rebase-update-refs-symrefs (2026年07月22日) 2 commits
 - rebase: guard non-branch symref targets
 - rebase: skip branch symref aliases
 'git rebase --update-refs' has been taught to resolve local branch
 symrefs to their referents before queuing updates, ensuring aliases of
 the current branch are skipped and duplicate updates are avoided to
 prevent failures when branch aliases are present.
 Waiting for response.
 cf. <5bece313-6ffb-450b-add1-29652b64de10@xxxxxxxxx>
 cf. <00e529b6-7ae7-463f-a4b3-0991e9411aba@xxxxxxxxx>
 cf. <amSSYagL0jTgzElD@mbp>
 cf. <xmqq7bmhycxq.fsf@gitster.g>
 source: <pull.2126.v3.git.1784708107.gitgitgadget@xxxxxxxxx>
* bc/rust-hash-cleanups (2026年07月18日) 2 commits
 (merged to 'next' on 2026年07月21日 at 51627468a0)
 + rust: discard hash context when finished
 + hash: initialize context before cloning
 A few memory problems in the Rust interface to C hash functions have
 been corrected. The 'Clone' implementation of 'CryptoHasher' now
 properly initializes the context before cloning, and its 'Drop'
 implementation now discards the context to prevent leaks.
 Will merge to 'master'.
 cf. <20260719080754.GA429688@xxxxxxxxxxxxxxxxxxxxxxx>
 source: <20260719010842.17991-1-sandals@xxxxxxxxxxxxxxxxxxxx>
* ja/doc-synopsis-style-yet-more (2026年07月23日) 4 commits
 - doc: convert git-request-pull synopsis and options to new style
 - doc: convert git-send-email synopsis and options to new style
 - doc: convert git-format-patch synopsis and options to new style
 - doc: convert git-imap-send synopsis and options to new style
 Synopsis and options in the documentation for 'git format-patch',
 'git imap-send', 'git send-email', and 'git request-pull' have been
 updated to the modern style.
 Needs review.
 source: <pull.2185.v2.git.1784841567.gitgitgadget@xxxxxxxxx>
* hn/url-push-tracking (2026年07月22日) 2 commits
 (merged to 'next' on 2026年07月25日 at 9b776656fc)
 + remote: find tracking branches for URL push destinations
 + remote: pass repository to push tracking helper
 When the push remote is specified as a URL, the fetch refspec of a
 uniquely matching configured remote is now used to find and update
 the remote-tracking branch (e.g., '@{push}').
 Will merge to 'master'.
 cf. <xmqqpl0eoniz.fsf@gitster.g>
 source: <pull.2358.v4.git.git.1784743738.gitgitgadget@xxxxxxxxx>
* tl/gitweb-shorten-hashes-with-modes (2026年07月17日) 1 commit
 (merged to 'next' on 2026年07月25日 at 5b92e8a325)
 + gitweb: shorten index hashes with trailing file modes
 The object ID shortening and linking in the 'commitdiff' view of
 'gitweb' has been corrected to work even when the index line carries
 a trailing file mode.
 Will merge to 'master'.
 cf. <xmqqjyqu6u7i.fsf@gitster.g>
 source: <SA1PR10MB9977150C823C0751E53B150D5AF1C62@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
* kj/repo-info-more-path-keys (2026年07月26日) 7 commits
 - repo: add path.git-prefix path key
 - repo: add path.grafts with absolute and relative suffix formatting
 - repo: add path.index with absolute and relative suffix formatting
 - repo: add path.hooks with absolute and relative suffix formatting
 - repo: add path.objects with absolute and relative suffix formatting
 - repo: add path.superproject-working-tree with absolute and relative suffixes
 - repo: add path.toplevel with absolute and relative suffix formatting
 The 'git repo info' command has been taught more keys to output
 paths of various repository components (such as the working tree
 root, superproject working tree, object database, etc.), supporting
 both absolute and relative path formats.
 Needs review.
 source: <20260726104343.16933-1-jayatheerthkulkarni2005@xxxxxxxxx>
* sk/userdiff-swift (2026年07月20日) 1 commit
 (merged to 'next' on 2026年07月23日 at 45dbcc6307)
 + userdiff: add support for Swift
 Userdiff patterns for Swift have been added, with support for
 Swift-specific constructs such as attributes, modifiers, failable
 initializers, and generics.
 Will merge to 'master'.
 cf. <2a3a73c5-5e90-44a3-bf6a-6e98ce5e5a59@xxxxxxxx>
 cf. <7b541cd5-bd66-4675-818d-8e23eb1c9530@xxxxxxxx>
 source: <20260721065736.8747-1-diy2903@xxxxxxxxx>
* ps/odb-move-loose-object-writing (2026年07月17日) 10 commits
 (merged to 'next' on 2026年07月25日 at 244d577d93)
 + object-file: move logic to write loose objects
 + object-file: move `force_object_loose()`
 + object-file: force objects loose via generic interface
 + object-file: fix memory leak in `force_object_loose()`
 + odb: support setting mtime when writing objects
 + odb: lift object existence check out of the "loose" backend
 + odb: compute object hash in `odb_write_object_ext()`
 + t/u-odb-inmemory: implement wrapper for writing objects
 + odb: compute compat object ID in `odb_write_object_ext()`
 + Merge branch 'jt/receive-pack-use-odb-transactions' into HEAD
 The logic to write loose objects has been refactored and moved from
 'object-file.c' to the loose backend source file 'odb/source-loose.c',
 making the loose backend more self-contained. This is achieved by
 first refactoring force_object_loose() to use generic ODB write
 interfaces instead of loose-backend internals.
 Will merge to 'master'.
 cf. <xmqqecgzpm0y.fsf@gitster.g>
 source: <20260717-pks-odb-move-loose-object-writing-v1-0-46446a3cb5b7@xxxxxx>
* pw/rebase-fixup-fixes (2026年07月26日) 2 commits
 - rebase: remember fixup -c after skipping fixup/squash
 - rebase -i: fix counting of fixups after rebase --skip
 Two bugs in how 'git rebase' handles skipped 'fixup' and 'squash'
 commands have been fixed. One bug caused an incorrect commit count to
 be shown in the template message when multiple commands were skipped,
 and another prevented the editor from opening when the final command
 in a chain containing 'fixup -c' was skipped.
 Will merge to 'next'?
 cf. <xmqqse55tp1k.fsf@gitster.g>
 source: <cover.1785080337.git.phillip.wood@xxxxxxxxxxxxx>
* tc/last-modified-bloom (2026年07月17日) 4 commits
 - last-modified: keep per-path Bloom filters for wildcard pathspecs
 - last-modified: check pathspec against Bloom filter first
 - revision: expose check for paths maybe changed in Bloom filter
 - revision: move bloom keyvec precondition into function
 The 'git last-modified' command has been optimized by using Bloom
 filters. It now reuses revision walk filtering logic from 'git log'
 to pre-filter commits, and maintains per-path Bloom filters even when
 wildcard pathspecs are used.
 Waiting for a response.
 cf. <20260720094218.GA681989@xxxxxxxxxxxxxxxxxxxxxxx>
 cf. <alvulw2fk67duo8n@com-79390>
 source: <20260717-toon-speed-up-last-modified-v1-0-410418f18614@xxxxxxxxx>
* hn/bisect-reset-when-found (2026年07月20日) 2 commits
 (merged to 'next' on 2026年07月22日 at 1dc394ad9b)
 + bisect: add --reset-when-found to leave when done
 + bisect: let bisect_reset() optionally check out quietly
 The 'git bisect' command has been taught a
 '--reset-when-found[=<where>]' option that tells the command to
 automatically run 'git bisect reset' to jump back to the original
 state or to the found culprit.
 Will merge to 'master'.
 cf. <xmqqldb5d1d9.fsf@gitster.g>
 source: <pull.2335.v3.git.git.1784538619.gitgitgadget@xxxxxxxxx>
* js/coverity-unchecked-returns-fix (2026年07月14日) 11 commits
 - bisect: handle dup() failure when redirecting stdout
 - bisect: check get_terms return at all call sites
 - bisect: check strbuf_getline_lf return when reading terms
 - transport-helper: warn when export-marks file cannot be finalized
 - transport-helper: check dup() return in get_exporter
 - compat/pread: check initial lseek for errors
 - last-modified: handle repo_parse_commit() failures
 - reftable tests: check reftable_table_init_ref_iterator() return
 - reftable/block: check deflateInit() return value
 - config: propagate launch_editor() failure in show_editor()
 - http: die on curl_easy_duphandle failure in get_active_slot
 A handful of code paths have been corrected to check return values
 from functions like curl_easy_duphandle(), deflateInit(), lseek(),
 dup(), and strbuf_getline_lf(), resolving several Coverity warnings
 about unchecked returns.
 Waiting for response.
 cf. <alcvmX3b6y92KE4y@xxxxxx>
 cf. <alcvnm0xiOv5W0w_@xxxxxx>
 cf. <xmqqldbdqciy.fsf@gitster.g>
 cf. <xmqqh5m1qcfh.fsf@gitster.g>
 cf. <xmqqh5lui6wg.fsf@gitster.g>
 cf. <xmqqcxwii6wd.fsf@gitster.g>
 source: <pull.2179.git.1784069325.gitgitgadget@xxxxxxxxx>
* jk/diff-relative-cached-unmerged (2026年07月14日) 1 commit
 (merged to 'next' on 2026年07月25日 at 8829f9b348)
 + diff: ignore unmerged paths outside prefix with --relative --cached
 (this branch is used by jk/diff-relative-cached-unmerged-more.)
 'git diff --relative' running with '--cached' has been corrected to
 avoid a segfault when encountering unmerged paths outside the
 prefix.
 Will merge to 'master'.
 cf. <xmqqjyqwp9jh.fsf@gitster.g>
 source: <20260715060523.GA517940@xxxxxxxxxxxxxxxxxxxxxxx>
* jc/submodule-helper-avoid-zu (2026年07月15日) 1 commit
 (merged to 'next' on 2026年07月19日 at b12d5d76f5)
 + submodule--helper: avoid use of %zu for now
 An accidental use of the '%zu' format specifier in 'git
 submodule--helper' has been corrected to use 'PRIuMAX' and cast the
 value to 'uintmax_t' to avoid portability issues.
 Will merge to 'master'.
 source: <xmqq4ii0ko9t.fsf@gitster.g>
* ds/trace2-tolerate-failed-timestamp (2026年07月15日) 1 commit
 - trace2: tolerate failed timestamp formatting
 The 'trace2' telemetry library has been updated to tolerate failures
 from system calls like gettimeofday() and datetime formatting
 functions, replacing potential program crashes with blank placeholder
 timestamps in the traces.
 Waiting for response.
 cf. <alpXW5U6sndZtgqV@com-79390>
 cf. <c8d443a5-3cfb-4752-8716-cf0d8fadd9d3@xxxxxxxxx>
 cf. <xmqqzezlhgyo.fsf@gitster.g>
 cf. <al4yrXXoZiHLwSvE@com-79390>
 source: <pull.2178.git.1784131932489.gitgitgadget@xxxxxxxxx>
* mm/revision-pure-get-commit-action (2026年07月15日) 1 commit
 - revision: make get_commit_action() a pure predicate
 The get_commit_action() function has been refactored to be a pure
 predicate by moving the side-effecting line-level log range folding to
 simplify_commit(). This ensures that evaluating a commit's action
 before the walk reaches it does not prematurely mutate its tracked
 line ranges, making it safer for potential lookahead evaluations.
 Waiting for review.
 cf. <xmqqjyqk3w7d.fsf@gitster.g>
 cf. <CAC2QwmKP16cyw0get3hEWP8GjcFkUHB3uXxcQi9hBCCM-B+ECw@xxxxxxxxxxxxxx>
 source: <pull.2169.git.1784143793613.gitgitgadget@xxxxxxxxx>
* rs/remote-curl-simplify-push-specs (2026年07月14日) 1 commit
 (merged to 'next' on 2026年07月19日 at ff1b5528ba)
 + remote-curl: simplify passing of push specs
 The passing of push destination specifications in the 'remote-curl'
 helper has been simplified by removing the explicit 'count' parameter
 and relying on the NULL-termination of the array.
 Will merge to 'master'.
 source: <935883f3-3be4-4c51-9711-5208b9ef9ca1@xxxxxx>
* cc/fast-import-usage (2026年07月16日) 7 commits
 - fast-import: use struct option for usage string
 - fast-import: move command state globals into 'struct fast_import_state'
 - fast-import: introduce 'struct fast_import_state'
 - fast-import: localize 'i' into the 'for' loops using it
 - api-parse-options.adoc: document hidden and OPT_*_F option macros
 - api-parse-options.adoc: document per-option flags
 - parse-options: introduce OPT_HIDDEN_GROUP
 The usage string of 'git fast-import' has been updated to use the
 parse_options() API for displaying help, and its SYNOPSIS in the
 documentation has been standardized to match.
 Waiting for response.
 cf. <xmqq4ihyehyb.fsf@gitster.g>
 cf. <xmqqcxwmeiwq.fsf@gitster.g>
 source: <20260716165517.433849-1-christian.couder@xxxxxxxxx>
* ps/copy-wo-the-repository (2026年07月16日) 1 commit
 (merged to 'next' on 2026年07月20日 at 9e38da0efc)
 + copy: drop dependency on `the_repository`
 The copy_file() and copy_file_with_time() functions have been
 refactored to take a repository parameter, allowing the removal of the
 implicit dependency on the global 'the_repository' variable in
 'copy.c'.
 Will merge to 'master'.
 cf. <b0df688a-3b26-48f6-8b1c-98530483885e@xxxxxxxxx>
 cf. <xmqqo6g54k7m.fsf@gitster.g>
 source: <20260716-pks-copy-wo-the-repository-v2-1-8f5e32942929@xxxxxx>
* ps/refspec-wo-the-repository (2026年07月16日) 3 commits
 (merged to 'next' on 2026年07月20日 at 31044c3fc9)
 + refspec: stop depending on `the_repository`
 + refspec: let callers pass in hash algorithm when parsing items
 + refspec: group related structures and functions
 The dependency on the global 'the_repository' variable in the
 'refspec.c' API has been removed by passing the hash algorithm
 explicitly to refspec-parsing functions and storing it in 'struct
 refspec'.
 Will merge to 'master'.
 source: <20260716-pks-refspec-wo-the-repository-v1-0-aa40844d067f@xxxxxx>
* ps/writev (2026年07月16日) 5 commits
 - fast-import: use writev(3p) to send cat-blob responses
 - sideband: use writev(3p) to send pktlines
 - wrapper: properly handle MAX_IO_SIZE in writev(3p)
 - wrapper: introduce writev(3p) wrappers
 - compat/posix: introduce writev(3p) wrapper
 A compatibility wrapper for writev(3p) has been reintroduced,
 including fixes for CMake build and 'MAX_IO_SIZE' limits on NonStop.
 Calls to write(3p) in send_sideband() and cat_blob() have been
 refactored to use writev(3p) wrappers to reduce syscall overhead.
 Waiting for response.
 cf. <f8050598-392f-44c9-8d66-0454740a7a12@xxxxxxxx>
 cf. <a2676ec6-39d5-4220-8549-10a17daec668@xxxxxxxxxx>
 cf. <xmqqwluuekbh.fsf@gitster.g>
 source: <20260716-pks-reintroduce-writev-v1-0-ea9038c884bc@xxxxxx>
* sc/wt-status-avoid-quadratic-insertion (2026年07月18日) 1 commit
 (merged to 'next' on 2026年07月20日 at 9330d42a4a)
 + wt-status: avoid repeated insertion for untracked paths
 The enumeration of untracked and ignored files in 'git status' has
 been optimized by avoiding quadratic complexity when inserting into
 string lists, reducing the construction cost from O(n^2) to O(n log
 n).
 Will merge to 'master'.
 cf. <20260718083828.GE22588@xxxxxxxxxxxxxxxxxxxxxxx>
 source: <20260718081449.26747-1-sahityajb@xxxxxxxxx>
* tb/send-pack-no-ref-delta (2026年07月12日) 4 commits
 - send-pack: honor `no-ref-delta` capability
 - pack-objects: support reuse with `--no-ref-delta`
 - pack-objects: introduce `--no-ref-delta`
 - t/helper: teach pack-deltas to list delta entries
 'git send-pack' has been taught to refrain from sending 'REF_DELTA'
 encoded packfiles when the other side asks it to.
 Needs review.
 source: <alQ7WKITYDXfiVn9@com-79390>
* tn/packfile-uri-concurrency (2026年07月25日) 3 commits
 - fetch-pack: accept "pack" output for packfile URIs
 - http: avoid concurrent appends to partial packs
 - http-fetch: correct --index-pack-arg documentation
 Concurrent downloads of packfiles via packfile URIs and dumb HTTP have
 been made safer by avoiding concurrent appends to the staging file.
 Opening the file in read-write mode and maintaining separate file
 offsets prevents corruption while preserving resumability. The
 'fetch-pack' command has also been updated to tolerate pre-existing
 '.keep' files.
 Expecting a reroll.
 cf. <20260726092027.GA3529827@xxxxxxxxxxxxxxxxxxxxxxx>
 cf. <20260726102712.GA3535709@xxxxxxxxxxxxxxxxxxxxxxx>
 cf. <20260726100421.12648-1-tnyman@xxxxxxxxxx>
 source: <cover.1785047139.git.tnyman@xxxxxxxxxx>
* rs/tempfile-wo-the-repository (2026年07月14日) 5 commits
 (merged to 'next' on 2026年07月22日 at 968a116891)
 + use repo_hold_lock_file_for_update{,_mode,_timeout}() with custom repos
 + tempfile: stop using the_repository
 + lockfile: add repo_hold_lock_file_for_update{,_timeout}{,_mode}()
 + refs/packed: use repo_create_tempfile()
 + tempfile: add repo_create_tempfile{,_mode}()
 The tempfile and lockfile APIs have been refactored to stop depending
 on the 'the_repository' global variable, and their callers have been
 updated to use the repository-aware variants.
 Will merge to 'master'.
 cf. <xmqq8q7ds3ld.fsf@gitster.g>
 cf. <xmqqmrvmn6a5.fsf@gitster.g>
 source: <20260714175956.54601-1-l.s.r@xxxxxx>
* js/pack-objects-delta-size-t (2026年07月09日) 12 commits
 - git-zlib: widen `git_deflate_bound()` to `size_t`
 - t/helper/test-pack-deltas: widen `do_compress()`'s maxsize local to `size_t`
 - http-push: widen `start_put()`'s size local from `ssize_t` to `size_t`
 - diff: widen `deflate_it()`'s bound local from int to `size_t`
 - archive-zip: widen `zlib_deflate_raw()`'s maxsize local to `size_t`
 - packfile, git-zlib: widen `use_pack()` and zstream avail fields to `size_t`
 - delta: widen `create_delta()` and `diff_delta()` to `size_t`
 - pack-objects: widen `mem_usage` and `try_delta()`'s out-param to `size_t`
 - pack-objects: widen `free_unpacked()` return to `size_t`
 - pack-objects: widen delta-cache accounting to `size_t`
 - delta: widen `create_delta_index()` parameter to `size_t`
 - diff-delta: widen `struct delta_index`' size fields to `size_t`
 The 'pack-objects' and delta-encoding code paths have been updated to
 use 'size_t' instead of 'unsigned long' for object sizes and offset
 limits, avoiding potential truncation issues on 64-bit Windows.
 Needs review.
 source: <pull.2175.git.1783615780.gitgitgadget@xxxxxxxxx>
* pz/fetch-submodule-errors-config (2026年07月16日) 2 commits
 - fetch: add fetch.submoduleErrors to make submodule fetch errors non-fatal
 - submodule: fix premature failure in recursive submodule fetch
 The 'git fetch' command has been updated to allow configuring how
 submodule fetch errors are handled. A new configuration variable
 'fetch.submoduleErrors' and a corresponding '--submodule-errors'
 command-line option have been introduced, allowing users to make
 submodule fetch errors non-fatal (warn instead of fail).
 Additionally, a premature failure during recursive submodule fetches
 has been fixed by deferring the error until the OID-based retry phase
 also fails.
 Needs review.
 source: <20260716140956.1023740-1-paulius.zaleckas@xxxxxxxxx>
* gr/add-e-use-apply-api (2026年07月10日) 1 commit
 - builtin/add.c: replace run_command() with direct apply_all_patches() call
 The application of the edited patch in 'git add -e' has been
 refactored to use the internal apply API directly, avoiding the need
 to spawn a 'git apply' subprocess.
 Needs review.
 cf. <xmqqechab03t.fsf@gitster.g>
 source: <20260711061246.58079-1-gatlavishweshwarreddy26@xxxxxxxxx>
* fz/rebase-autosquash-empty (2026年07月11日) 1 commit
 . sequencer: honor --empty when a fixup!/squash! empties its target
 A commit that is emptied by melding a 'fixup!' or 'squash!' commit
 during 'git rebase --autosquash' is now handled according to the
 '--empty' option, allowing it to be dropped, kept, or to halt the
 rebase.
 Ejected due to conflicts with 'pw/rebase-drop-notes-with-commit'.
 Waiting for response.
 cf. <690b965e-5f07-4aa4-a64c-96e60a86d73b@xxxxxxxxx>
 cf. <xmqqh5m494yh.fsf@gitster.g>
 cf. <b4cf8f14-1ffa-4395-bc3e-936538574665@xxxxxxxxx>
 source: <20260711-fz-autosquash-empty-v3-1-d227b63eb511@xxxxxxxxx>
* mm/lib-httpd-cgi-safe (2026年07月10日) 3 commits
 - t/README: document writing concurrency-safe helpers
 - t/lib-httpd: make http-429 first-request check atomic
 - t/lib-httpd: fix apply-one-time-script race under concurrent requests
 CGI helper scripts used by HTTP-related test scripts have been updated
 to use atomic filesystem operations, preventing race conditions when
 Apache handles concurrent requests.
 Needs review.
 source: <pull.2171.v2.git.1783704657.gitgitgadget@xxxxxxxxx>
* ps/odb-pluggable-housekeeping (2026年07月12日) 12 commits
 - odb: make optimizations pluggable
 - builtin/gc: fix signedness issues in ODB-related functionality
 - builtin/gc: refactor ODB optimizations to operate on "files" source
 - builtin/gc: introduce `odb_optimize_required()`
 - builtin/gc: move geometric repacking into `odb_optimize()`
 - builtin/gc: introduce object database optimization options
 - builtin/gc: inline config values specific to the "files" backend
 - builtin/gc: make repack arguments self-contained
 - builtin/gc: extract object database optimizations into separate function
 - builtin/gc: move worktree and rerere tasks before object optimizations
 - odb: run "pre-auto-gc" hook for all maintenance tasks
 - t7900: simplify how we check for maintenance tasks
 Object database housekeeping in 'git gc' and 'git maintenance' has
 been refactored to be pluggable. The files-backend-specific logic,
 including incremental and geometric repacking as well as object
 pruning, has been moved out of the command implementation and into the
 files object database source, enabling future alternative object
 database backends to implement their own housekeeping services.
 Waiting for response.
 cf. <xmqqh5m2yhkm.fsf@gitster.g>
 cf. <xmqqwluyyhv1.fsf@gitster.g>
 cf. <amCmwKjbq2aNt8mZ@xxxxxx>
 cf. <xmqqwluhvhtu.fsf@gitster.g>
 source: <20260713-b4-pks-odb-optimize-v2-0-9c2c3ee94b38@xxxxxx>
* ps/refs-wo-the-repository (2026年07月15日) 7 commits
 (merged to 'next' on 2026年07月19日 at 12685f410c)
 + refs: remove remaining uses of `the_repository`
 + worktree: pass repository to public functions
 + worktree: pass repository to file-local functions
 + worktree: refactor code to use available repositories
 + refs/files: drop `USE_THE_REPOSITORY_VARIABLE`
 + refs/packed: de-globalize handling of "core.packedRefsTimeout"
 + Merge branch 'ps/refs-writing-subcommands' into ps/refs-wo-the-repository
 The ref subsystem and the worktree API have been refactored to pass a
 repository pointer down the call chain, allowing them to drop
 references to the global 'the_repository' variable. As part of this,
 the handling of the 'core.packedRefsTimeout' configuration has been
 moved into the per-repository ref store structure.
 Will merge to 'master'.
 source: <20260716-pks-refs-wo-the-repository-v3-0-db0a804e0224@xxxxxx>
* ds/sparse-index-ita-crash (2026年07月06日) 1 commit
 - sparse-index: avoid crash on intent-to-add entry outside the cone
 A crash in the 'sparse-index' collapse code when encountering an
 invalidated cache-tree node (due to an intent-to-add path) has been
 fixed by avoiding collapsing such subtrees.
 Needs review.
 source: <pull.2167.git.1783345853272.gitgitgadget@xxxxxxxxx>
* ij/subtree-reject-v2-config (2026年07月06日) 2 commits
 - git-subtree: Bail out if we find output from Rust rewrite (test)
 - git-subtree: Bail out if we find output from Rust rewrite
 The shell script implementation of 'git subtree' has been updated to
 check for the presence of the configuration file of the new Rust
 implementation, preventing users from accidentally running the old
 script on repositories already managed by the new tool.
 Expecting a reroll.
 cf. <27219.20156.438730.881821@xxxxxxxxxxxxxxxxxxxxxx>
 source: <20260706115816.20267-1-ijackson@xxxxxxxxxxxxxxxxxxxxxx>
* jm/t0213-skip-emulated-ancestry-tests (2026年07月06日) 1 commit
 - t0213: skip ancestry tests under user-mode emulation
 The 'TRACE2_ANCESTRY' prerequisite in the 't0213' test script has been
 refined to avoid failures under user-mode emulation by verifying that
 the ancestry collector reports the expected process names rather than
 the emulator binary name.
 Needs review.
 cf. <xmqq33xcz2i7.fsf@gitster.g>
 source: <pull.2168.git.1783359242130.gitgitgadget@xxxxxxxxx>
* zy/apply-abandoned-header-fix (2026年07月01日) 1 commit
 - apply: avoid leaking abandoned git-header state
 A candidate 'git diff' header parsed by 'git apply' has been isolated
 in a temporary structure, preventing any partially parsed state from
 polluting the main patch structure and causing assertions to trip if
 the header is ultimately rejected.
 Needs review.
 source: <20260702041759.51572-1-zhihao.yao@xxxxxxxx>
* bl/t7412-use-test-path-helpers (2026年06月29日) 1 commit
 - submodule absorbgitdirs tests: use test_* helper functions
 The test script 't7412' that tests 'git submodule absorbgitdirs' has
 been modernized to use test_path_is_file(), test_path_is_dir(), and
 test_path_is_missing() helper functions instead of raw 'test -[fde]'
 commands.
 Waiting for response, stalled.
 cf. <xmqqmrwbsybn.fsf@gitster.g>
 cf. <akTKHfKPsP3-Rn31@xxxxxx>
 source: <20260630020220.1559190-1-bblima@xxxxxx>
* pw/rebase-drop-notes-with-commit (2026年07月15日) 9 commits
 (merged to 'next' on 2026年07月20日 at 5475c9f935)
 + sequencer: do not record dropped commits as rewritten
 + sequencer: use an enum to represent result of picking a commit
 + sequencer: simplify pick_one_commit()
 + sequencer: remove unnecessary condition in pick_one_commit()
 + sequencer: simplify handling of fixup with conflicts
 + sequencer: remove unnecessary "or" in pick_one_commit()
 + sequencer: never reschedule on failed commit
 + sequencer: be more careful with external merge
 + t3400: restore coverage for note copying with apply backend
 The rebase post-rewrite notes-copying logic has been corrected. When
 a commit is dropped during rebase (e.g., because its changes are
 already upstream), it is no longer recorded as rewritten, preventing
 its notes from being copied to an unrelated commit.
 Will merge to 'master'.
 cf. <xmqqy0f5d25g.fsf@gitster.g>
 source: <cover.1784128921.git.phillip.wood@xxxxxxxxxxxxx>
* ty/migrate-excludes-file (2026年07月13日) 10 commits
 (merged to 'next' on 2026年07月23日 at 749560a29c)
 + repository: adjust the comment of config_values_private_
 + environment: move object_creation_mode into repo_config_values
 + environment: move autorebase into repo_config_values
 + environment: move push_default into repo_config_values
 + environment: migrate apply_default_whitespace and apply_default_ignorewhitespace
 + environment: move askpass_program into repo_config_values
 + environment: move pager_program into repo_config_values
 + environment: move editor_program into repo_config_values
 + environment: move excludes_file into repo_config_values
 + repository: introduce repo_config_values_clear()
 The 'excludes_file' and various other global configuration variables
 (including 'editor_program', 'pager_program', 'askpass_program', and
 'push_default') have been migrated into the per-repository structure.
 Will merge to 'master'.
 cf. <xmqqa4ruyhbh.fsf@gitster.g>
 source: <20260714032525.1611141-1-cat@xxxxxxxxx>
* ps/libgit-in-subdir (2026年07月12日) 3 commits
 . Move libgit.a sources into separate "lib/" directory
 . t/helper: prepare "test-example-tap.c" for introduction of "lib/"
 . Merge branch 'ps/odb-source-packed' into ps/libgit-in-subdir
 The source files for 'libgit.a' have been moved into a new 'lib/'
 directory to clean up the top-level directory and clearly separate
 library code.
 Ejected for now, as it causes too many evil merges with other topics.
 Waiting for response.
 cf. <xmqqqzkx9t95.fsf@gitster.g>
 cf. <xmqqjyqpb96n.fsf@gitster.g>
 cf. <al6Yz_QMlyU1GETv@xxxxxxxxxxxxxxxxxxxxxxxxxx>
 source: <20260713-pks-libgit-in-subdir-v4-0-696240876eb1@xxxxxx>
* mm/line-log-limited-ops (2026年06月27日) 7 commits
 - diffcore-pickaxe: scope -G to the -L tracked range
 - diff: support --check with -L line ranges
 - line-log: support diff stat formats with -L
 - diff: extract a line-range diff helper for reuse
 - diff: emit -L hunk headers via xdiff's formatter
 - diff: simplify the line-range filter by classifying removals immediately
 - diff: rename and group the line-range filter for clarity
 (this branch is used by mm/diff-process-hunks.)
 The 'git log -L<range>:<path>' command has been taught to limit
 various 'diff' operations, such as '--stat', '--check', and '-G', to
 the specified range and path.
 Needs review.
 cf. <xmqq8q8bpl03.fsf@gitster.g>
 source: <pull.2152.v2.git.1782581342.gitgitgadget@xxxxxxxxx>
* hn/history-squash (2026年07月20日) 5 commits
 (merged to 'next' on 2026年07月23日 at 2790c83e45)
 + history: re-edit a squash with every message
 + sequencer: share the squash message marker helpers and flags
 + history: add squash subcommand to fold a range
 + history: give commit_tree_ext a message template
 + history: extract helper for a commit's parent tree
 The experimental 'git history' command has been taught a new 'squash'
 subcommand to fold a range of commits into a single commit, with any
 descendants replayed on top.
 Will merge to 'master'.
 cf. <DK1KIF2OI8IF.11188A3YEQV1C@xxxxxxxxx>
 cf. <DK1KIH6CXW0X.1U2V3GU8L6HB7@xxxxxxxxx>
 source: <pull.2337.v10.git.git.1784536024.gitgitgadget@xxxxxxxxx>
* tb/midx-incremental-custom-base (2026年06月12日) 3 commits
 - midx-write: include packs above custom incremental base
 - midx: pass custom '--base' through incremental writes
 - t5334: expose shared `nth_line()` helper
 The 'git multi-pack-index write --incremental' command has been
 corrected to properly honor the '--base' option. Previously, the
 custom base was ignored by the normal write path; packs from layers
 above the selected base were incorrectly skipped by the pack exclusion
 logic, and reachability closure for bitmaps was broken.
 Needs review.
 source: <cover.1781294771.git.me@xxxxxxxxxxxx>
* td/ref-filter-memoize-contains (2026年06月12日) 3 commits
 (merged to 'next' on 2026年07月19日 at 5b640e33a1)
 + commit-reach: die on contains walk errors
 + ref-filter: memoize --contains with generations
 + commit-reach: reject cycles in contains walk
 'git branch --contains' and 'git for-each-ref --contains' have been
 optimized to use the memoized commit traversal previously used only by
 'git tag --contains', significantly speeding up connectivity checks
 across many candidate refs with shared history.
 Will merge to 'master'.
 cf. <20260716091924.GB1212956@xxxxxxxxxxxxxxxxxxxxxxx>
 source: <20260612-ref-filter-memoized-contains-v4-0-5ed39fd001dd@xxxxxxxxx>
* tc/replay-linearize (2026年07月07日) 3 commits
 (merged to 'next' on 2026年07月09日 at 371c2e9c3b)
 + replay: offer an option to linearize the commit topology
 + replay: resolve the replay base outside pick_regular_commit()
 + replay: add helper to put entry into replayed_commits
 The 'git replay' command has been taught the '--linearize' option to
 drop merge commits and linearize the replayed history, mimicking 'git
 rebase --no-rebase-merges'.
 On hold, waiting for response from the author.
 cf. <xmqq5x2qz42z.fsf@gitster.g>
 cf. <CABPp-BGzU9KHGF1nipi2HZaa1AiikMKGGaapQzHVH06wO4V1ww@xxxxxxxxxxxxxx>
 source: <20260707-toon-git-replay-drop-merges-v7-0-808ab9b4afa6@xxxxxxxxx>
* ps/cat-file-remote-object-info (2026年07月24日) 13 commits
 (merged to 'next' on 2026年07月24日 at e436a42272)
 + cat-file: make remote-object-info allow-list adapt to the server
 + cat-file: add remote-object-info to batch-command
 + transport: add client support for object-info
 + serve: advertise object-info feature
 + protocol-caps: check object existence regardless of the attributes requested
 + fetch-pack: move fetch initialization
 + connect: make write_fetch_command_and_capabilities() more generic
 + fetch-pack: move write_fetch_command_and_capabilities() to connect.c
 + fetch-pack: use unsigned int for hash_algo variable
 + fetch-pack: drop the static advertise_sid variable
 + t1006: extract helper functions into new 'lib-cat-file.sh'
 + cat-file: declare loop counter inside for()
 + transport-helper: fix memory leak of helper on disconnect
 (this branch is used by ps/cat-file-remote-object-info-type.)
 The 'remote-object-info' command has been added to 'git cat-file
 --batch-command', allowing clients to request object metadata
 (currently size) from a remote server via protocol v2 without
 downloading the entire object. Format placeholders are dynamically
 filtered on the client based on server-advertised capabilities,
 returning empty strings for inapplicable or unsupported fields.
 Will merge to 'master'.
 source: <20260724-ps-eric-work-rebase-v21-0-ba67f024fdff@xxxxxxxxx>
* mm/diff-process-hunks (2026年07月26日) 10 commits
 - line-log: consult diff process for range tracking
 - diff: consult diff process for --stat counts
 - blame: consult diff process for no-hunk detection
 - diff: bypass diff process with --no-ext-diff and in format-patch
 - diff: add long-running diff process via diff.<driver>.process
 - sub-process: separate process lifecycle from hashmap management
 - userdiff: add diff.<driver>.process config
 - xdiff: support external hunks via xpparam_t
 - gitattributes: document how external diff drivers relate to diff features
 - Merge branch 'mm/line-log-limited-ops' into mm/diff-process-hunks
 (this branch uses mm/line-log-limited-ops.)
 A new 'diff.<driver>.process' configuration has been introduced to
 allow a long-running external process to act as a hunk provider,
 enabling external tools to control which lines Git considers changed
 while leaving all output formatting (word diff, color, blame, etc.) to
 Git's standard pipeline.
 Ejected for now, as it conflicts badly with 'mm/line-log-limited-ops'.
 Needs review.
 source: <pull.2120.v6.git.1785091889.gitgitgadget@xxxxxxxxx>
* ty/migrate-trust-executable-bit (2026年07月20日) 4 commits
 (merged to 'next' on 2026年07月23日 at 4873f289dd)
 + environment: move has_symlinks into repo_config_values
 + environment: move trust_executable_bit into repo_config_values
 + read-cache: pass 'repo' to 'ce_mode_from_stat()'
 + read-cache: remove redundant extern declarations
 The 'trust_executable_bit' (coming from the 'core.filemode'
 configuration) has been migrated into 'struct repo_config_values' to
 tie it to a specific repository instance.
 Will merge to 'master'.
 cf. <alvNq8rXF/jofqUc@xxxxxxxxxx>
 cf. <xmqq8q7961xe.fsf@gitster.g>
 source: <20260720105335.3202013-1-cat@xxxxxxxxx>
* ec/commit-fixup-options (2026年05月26日) 2 commits
 - commit: allow -c/-C for all kinds of --fixup
 - commit: allow -m/-F for all kinds of --fixup
 Support for '-m', '-F', '-c', or '-C' options to supply a commit log
 message from outside the editor has been added for all 'git commit
 --fixup' variations.
 Needs review.
 source: <cover.1779792311.git.erik@xxxxxxxxxxx>
* hn/branch-delete-merged (2026年07月25日) 7 commits
 - branch: add --dry-run for --delete-merged
 - branch: add branch.<name>.deleteMerged opt-out
 - branch: add --delete-merged <branch>
 - branch: prepare delete_branches for a bulk caller
 - branch: let delete_branches skip unmerged branches on bulk refusal
 - branch: convert delete_branches() to a flags argument
 - branch: add --forked filter for --list mode
 The 'git branch' command has been taught the '--delete-merged' option
 to remove local branches that are already merged into their tracked
 remote-tracking branches.
 Will merge to 'next'?
 cf. <xmqqy0ez14s9.fsf@gitster.g>
 source: <pull.2285.v23.git.git.1784979136.gitgitgadget@xxxxxxxxx>
* ps/shift-root-in-graph (2026年07月14日) 7 commits
 (merged to 'next' on 2026年07月19日 at bebf13a239)
 + graph: add --[no-]graph-indent and log.graphIndent
 + graph: move config reading into graph_read_config()
 + graph: wrap cascading commits after 4 columns
 + graph: indent visual root in graph
 + graph: add a 2 commit buffer for lookahead
 + revision: add next_commit_to_show()
 + lib-log-graph: move check_graph function
 'git log --graph' has been modified to visually distinguish parentless
 'root' commits (and commits that become roots due to history
 simplification) by indenting them, preventing them from appearing
 falsely related to unrelated commits rendered immediately above them.
 Will merge to 'master'.
 cf. <CA+J6zkQNzEAhhY74qDrOwfFVrshEF7YFxWRRkwE3ttJo15ZbAg@xxxxxxxxxxxxxx>
 source: <20260714-ps-pre-commit-indent-v12-0-d50938e006df@xxxxxxxxx>
* kk/merge-base-exhaustion (2026年07月11日) 11 commits
 - commit-reach: remove commit-date ordering fallback
 - commit-reach: move min_generation check into paint_queue_get()
 - commit-reach: terminate merge-base walk when one paint side is exhausted
 - commit-reach: introduce struct paint_state with per-side counters
 - t6600: add clock-skew topologies and step counts for edge cases
 - commit-reach: add trace2 instrumentation to paint_down_to_common()
 - t6099, t6600: add side-exhaustion regression tests
 - t6600: add test cases for side-exhaustion edge cases
 - test-lib-functions: improve diagnostic output for trace2 data assertions
 - Documentation/technical: add paint-down-to-common doc
 - Merge branch 'kk/commit-reach-find-all-fix' into kk/merge-base-exhaustion
 The merge-base computation has been optimized by stopping the walk
 early when one side's exclusive commits in the queue are exhausted,
 yielding significant speedups for queries with one-sided histories.
 Needs review.
 cf. <CABPp-BGATrNJyT7trzUzAMB_v-1ssVe_SRqp+281X5GzU=2eow@xxxxxxxxxxxxxx>
 source: <pull.2149.v6.git.1783776466.gitgitgadget@xxxxxxxxx>

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

(追記) (追記ここまで)
Powered by Linux

AltStyle によって変換されたページ (->オリジナル) /