{"thread":{"id":"63933","subject":"What's cooking in git.git (Aug 2025, #03; Fri, 8)","startedAt":"2025-08-09T03:28:22Z","lastAt":"2025-08-11T15:41:22Z","messageCount":3,"participants":["Junio C Hamano","Eric Sunshine"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"523863","messageId":"xmqqectl6unf.fsf@gitster.g","threadId":"63933","inReplyTo":null,"subject":"What's cooking in git.git (Aug 2025, #03; Fri, 8)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-08-09T03:28:20Z","receivedAt":"2025-08-09T03:28:22Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Here are the topics that have been cooking in my tree. Commits\nprefixed with '+' are in 'next' (being in 'next' is a sign that a\ntopic is stable enough to be used and are candidate to be in a\nfuture release). Commits prefixed with '-' are only in 'seen', and\naren't considered \"accepted\" at all and may be annotated with an URL\nto a message that raises issues but they are no means exhaustive. A\ntopic without enough support may be discarded after a long period of\nno activity (of course they can be resubmit when new interests\narise).\n\nCopies of the source code to Git live in many repositories, and the\nfollowing is a list of the ones I push into or their mirrors. Some\nrepositories have only a subset of branches.\n\nWith maint, master, next, seen, todo:\n\n\tgit://git.kernel.org/pub/scm/git/git.git/\n\tgit://repo.or.cz/alt-git.git/\n\thttps://kernel.googlesource.com/pub/scm/git/git/\n\thttps://github.com/git/git/\n\thttps://gitlab.com/git-scm/git/\n\nWith all the integration branches and topics broken out:\n\n\thttps://github.com/gitster/git/\n\nEven though the preformatted documentation in HTML and man format\nare not sources, they are published in these repositories for\nconvenience (replace \"htmldocs\" with \"manpages\" for the manual\npages):\n\n\tgit://git.kernel.org/pub/scm/git/git-htmldocs.git/\n\thttps://github.com/gitster/git-htmldocs.git/\n\nRelease tarballs are available at:\n\n\thttps://www.kernel.org/pub/software/scm/git/\n\n--------------------------------------------------\n[Graduated to 'master']\n\n* dl/squelch-maybe-uninitialized (2025-08-04) 2 commits\n (merged to 'next' on 2025-08-05 at fa3c3830ee)\n + t/unit-tests/clar: fix -Wmaybe-uninitialized with -Og\n + remote: bail early from set_head() if missing remote name\n\n Squelch false-positive compiler warning.\n source: \n\n\n* jk/revert-squelch-compiler-warning (2025-08-04) 1 commit\n (merged to 'next' on 2025-08-05 at 344a6a715b)\n + revert: initialize const value\n\n Squelch false-positive compiler warning.\n source: <20250804130011.GA93475@coredump.intra.peff.net>\n\n\n* jt/archive-zip-deflate-fix (2025-08-02) 1 commit\n (merged to 'next' on 2025-08-06 at 1a5c1ccec3)\n + archive: flush deflate stream until Z_STREAM_END\n\n The deflate codepath in \"git archive --format=zip\" had a\n longstanding bug coming from misuse of zlib API, which has been\n corrected.\n source: <20250802220803.95137-1-jltobler@gmail.com>\n\n\n* kj/renamed-submodule (2025-07-24) 4 commits\n (merged to 'next' on 2025-08-03 at c341b36545)\n + fixup! submodule: skip redundant active entries when pattern covers path\n + fixup! submodule: prevent overwriting .gitmodules on path reuse\n + submodule: skip redundant active entries when pattern covers path\n + submodule: prevent overwriting .gitmodules on path reuse\n\n The case where a new submodule takes a path where used to be a\n completely different subproject is now dealt a bit better than\n before.\n source: <20250724152418.45226-1-jayatheerthkulkarni2005@gmail.com>\n\n\n* ps/object-file-wo-the-repository (2025-07-16) 17 commits\n (merged to 'next' on 2025-08-01 at 0c1253014e)\n + object-file: get rid of `the_repository` in index-related functions\n + object-file: get rid of `the_repository` in `force_object_loose()`\n + object-file: get rid of `the_repository` in `read_loose_object()`\n + object-file: get rid of `the_repository` in loose object iterators\n + object-file: remove declaration for `for_each_file_in_obj_subdir()`\n + object-file: inline `for_each_loose_file_in_objdir_buf()`\n + object-file: get rid of `the_repository` when writing objects\n + odb: introduce `odb_write_object()`\n + loose: write loose objects map via their source\n + object-file: get rid of `the_repository` in `finalize_object_file()`\n + object-file: get rid of `the_repository` in `loose_object_info()`\n + object-file: get rid of `the_repository` when freshening objects\n + object-file: inline `check_and_freshen()` functions\n + object-file: get rid of `the_repository` in `has_loose_object()`\n + object-file: stop using `the_hash_algo`\n + object-file: fix -Wsign-compare warnings\n + Merge branch 'ps/object-store' into ps/object-file-wo-the-repository\n\n Reduce implicit assumption and dependence on the_repository in the\n object-file subsystem.\n cf. <87ms8na1mc.fsf@iotcl.com>\n cf. \n source: <20250717-pks-object-file-wo-the-repository-v2-0-36d2cd6c700e@pks.im>\n\n\n* rs/tighten-alias-help (2025-07-25) 1 commit\n (merged to 'next' on 2025-08-01 at a0fb0696cd)\n + git: show alias info only with lone -h\n\n \"git -c alias.foo=bar foo -h baz\" reported \"'foo' is aliased to\n 'bar'\" and then went on to run \"git foo -h baz\", which was\n unexpected. Tighten the rule so that alias expansion is reported\n only when \"-h\" is the sole option.\n source: \n\n--------------------------------------------------\n[New Topics]\n\n* dl/push-missing-object-error (2025-08-08) 3 commits\n - remote.c: convert if-else ladder to switch\n - remote.c: remove BUG in show_push_unqualified_ref_name_error()\n - t5516: remove surrounding empty lines in test bodies\n\n \"git push\" had a code path that led to BUG() but it should have\n been a die(), as it is a response to a usual but invalid end-user\n action to attempt pushing an object that does not exist.\n\n Will merge to 'next'.\n cf. \n source: \n\n\n* ja/doc-lint-sections-and-synopsis (2025-08-05) 7 commits\n . fixup! doc: check for absence of multiple terms in each entry of desc list\n . doc lint: check that synopsis manpages have synopsis inlines\n . doc:git-for-each-ref: fix styling and typos\n . doc: check for absence of the form --[no-]parameter\n . doc: check for absence of multiple terms in each entry of desc list\n . doc: check well-formedness of delimited sections\n . doc: test linkgit macros for well-formedness\n\n Doc lint updates to encourage the newer and easier-to-use\n `synopsis` format, with fixes to a handful of existing uses.\n\n Comments?\n source: \n\n\n* js/rebase-i-allow-drop-on-a-merge (2025-08-06) 1 commit\n (merged to 'next' on 2025-08-07 at bc44e9dc1b)\n + rebase -i: permit 'drop' of a merge commit\n\n During interactive rebase, using 'drop' on a merge commit lead to\n an error, which was incorrect.\n\n Will cook in 'next'.\n source: <37f6e34c-91aa-4e55-88e1-019d2e042df3@kdbg.org>\n\n\n* ms/refs-list (2025-08-05) 6 commits\n - t: add test for git refs list subcommand\n - t6300: refactor tests to be shareable\n - builtin/refs: add list subcommand\n - builtin/for-each-ref: factor out core logic into a helper\n - builtin/for-each-ref: align usage string with the man page\n - doc: factor out common option\n\n The \"list\" subcommand of \"git refs\" acts as a front-end for\n \"git for-each-ref\".\n\n Comments?\n source: <20250805092758.5321-1-meetsoni3017@gmail.com>\n\n\n* kh/doc-git-log-markup-fix (2025-08-08) 1 commit\n - doc: git-log: fix description list\n\n Doc update.\n\n Will merge to 'next'.\n source: \n\n\n* ly/changed-path-traversal-with-magic-pathspec (2025-08-08) 2 commits\n - fixup! bloom: enable bloom filter with wildcard pathspec in revision traversal\n - bloom: enable bloom filter with wildcard pathspec in revision traversal\n\n Revision traversal limited with pathspec, like \"git log dir/*\",\n used to ignore changed-paths Bloom filter when the pathspec\n contained wildcards; now they take advantage of the filter when\n they can.\n\n Will merge to 'next'?\n source: <20250808065834.22743-1-yldhome2d2@gmail.com>\n\n\n* ps/commit-graph-wo-globals (2025-08-07) 10 commits\n - commit-graph: stop passing in redundant repository\n - commit-graph: stop using `the_repository`\n - commit-graph: stop using `the_hash_algo`\n - commit-graph: refactor `parse_commit_graph()` to take a repository\n - commit-graph: store the hash algorithm instead of its length\n - commit-graph: stop using `the_hash_algo` via macros\n - commit-graph: fix sign comparison warnings\n - commit-graph: fix type for some write options\n - commit-graph: stop using signed integers to count Bloom filters\n - trace2: introduce function to trace unsigned integers\n\n Remove dependency on the_repository and other globals from the\n commit-graph code, and other changes unrelated to de-globaling.\n\n Will merge to 'next'?\n source: <20250807-b4-pks-commit-graph-wo-the-repository-v3-0-82edef830a1e@pks.im>\n\n\n* tc/t0450-harden (2025-08-08) 2 commits\n . t0450: add allowlist for builtins with missing .adoc\n . t0450: fix test for out-of-tree builds\n\n Test updates.\n\n Will merge to 'next'.\n source: <20250804073002.1586332-1-toon@iotcl.com>\n\n\n* gh/git-jump-pathname-with-sp (2025-08-08) 1 commit\n - git-jump: make `diff` work with filenames containing spaces\n\n source: \n\n\n* jc/diff-no-index-in-subdir (2025-08-07) 1 commit\n - diff: --no-index should ignore the worktree\n\n source: \n\n\n* je/doc-rebase (2025-08-08) 5 commits\n - doc: git-rebase: update discussion of internals\n - doc: git-rebase: move --onto explanation down\n - doc: git rebase: clarify arguments syntax\n - doc: git rebase: dedup merge conflict discussion\n - doc: git-rebase: start with an example\n\n source: \n\n\n* rj/t6137-cygwin-fix (2025-08-08) 2 commits\n - git-jump: make `diff` work with filenames containing spaces\n - t6137-*.sh: fix test failure on cygwin\n\n source: \n\n--------------------------------------------------\n[Cooking]\n\n* ps/reftable-libgit2-cleanup (2025-08-04) 6 commits\n - reftable/stack: handle outdated stacks when compacting\n - reftable/stack: allow passing flags to `reftable_stack_add()`\n - reftable/stack: reorder code to avoid forward declarations\n - reftable/stack: fix compiler warning due to missing braces\n - reftable/writer: drop Git-specific `QSORT()` macro\n - reftable/writer: fix type used for number of records\n\n Code clean-ups.\n\n Comments?\n source: <20250804-pks-reftable-fixes-for-libgit2-v2-0-fef06209a984@pks.im>\n\n\n* tc/diff-tree-max-depth (2025-08-07) 3 commits\n - diff: teach tree-diff a max-depth parameter\n - within_depth: fix return for empty path\n - combine-diff: zero memory used for callback filepairs\n\n \"git diff-tree\" learned \"--max-depth\" option.\n\n Comments?\n source: <20250807-toon-max-depth-v2-0-50b7e5c81665@iotcl.com>\n\n\n* dk/help-all (2025-08-03) 3 commits\n - builtin: also setup gently for --help-all\n - parse-options: refactor flags for usage_with_options_internal\n - Merge branch 'ua/t1517-short-help-tests' into dk/help-all\n (this branch uses ua/t1517-short-help-tests.)\n\n \"git cmd --help-all\" outside repository.\n\n Comments?\n source: <20250803012613.54086-1-ben.knoble+github@gmail.com>\n\n\n* lc/rebase-trailer (2025-08-03) 2 commits\n - rebase: support --trailer\n - trailer: append trailers in-process and drop the fork to `interpret-trailers`\n\n Expecting a reroll.\n cf. <198826af571.62b85cb31711042.2415806544948206668@linux.beauty>\n source: <20250803150059.402017-1-me@linux.beauty>\n\n\n* ly/diff-name-only-with-diff-from-content (2025-08-07) 1 commit\n - diff: ensure consistent diff behavior with ignore options\n\n Various options to \"git diff\" that makes comparison ignore certain\n aspects of the differences (like \"space changes are ignored\",\n \"differences in lines that match these regular expressions are\n ignored\") did not work well with \"--name-only\" and friends.\n\n Will merge to 'next'?\n source: <20250808033019.78817-1-yldhome2d2@gmail.com>\n\n\n* rs/describe-with-prio-queue (2025-08-03) 2 commits\n (merged to 'next' on 2025-08-07 at 5ebcaaf8b8)\n + describe: use prio_queue_replace()\n + describe: use prio_queue\n\n \"git describe\" has been optimized by using better data structure.\n\n Will cook in 'next'.\n source: <36d5b59a-a99a-4a6f-b637-dfb0b760660f@web.de>\n\n\n* ps/object-store-midx-dedup-info (2025-08-07) 10 commits\n - midx: compute paths via their source\n - midx: stop duplicating info redundant with its owning source\n - midx: write multi-pack indices via their source\n - midx: load multi-pack indices via their source\n - midx: drop redundant `struct repository` parameter\n - odb: simplify calling `link_alt_odb_entry()`\n - odb: return newly created in-memory sources\n - odb: allow `odb_find_source()` to fail\n - odb: store locality in object database sources\n - Merge branch 'ps/object-store-midx' into ps/object-store-midx-dedup-info\n\n Further code clean-up for multi-pack-index code paths.\n\n Comments?\n source: <20250807-b4-pks-midx-deduplicate-source-info-v2-0-bcffb8fc119c@pks.im>\n\n\n* jc/strbuf-split (2025-07-31) 13 commits\n - trace2: do not use strbuf_split*()\n - trace2: trim_trailing_newline followed by trim is a no-op\n - sub-process: do not use strbuf_split*()\n - environment: do not use strbuf_split*()\n - config: do not use strbuf_split()\n - notes: do not use strbuf_split*()\n - merge-tree: do not use strbuf_split*()\n - clean: do not use strbuf_split*() [part 2]\n - clean: do not pass the whole structure when it is not necessary\n - clean: do not use strbuf_split*() [part 1]\n - clean: do not pass strbuf by value\n - wt-status: avoid strbuf_split*()\n - Merge branch 'jc/string-list-split' into jc/strbuf-split\n (this branch uses jc/string-list-split.)\n\n Arrays of strbuf is often a wrong data structure to use, and\n strbuf_split*() family of functions that create them often have\n better alternatives.\n\n Update several code paths and replace strbuf_split*().\n\n Will merge to 'next'.\n source: <20250731225433.4028872-1-gitster@pobox.com>\n\n\n* jc/string-list-split (2025-08-01) 7 commits\n - string-list: split-then-remove-empty can be done while splitting\n - string-list: optionally omit empty string pieces in string_list_split*()\n - diff: simplify parsing of diff.colormovedws\n - string-list: optionally trim string pieces split by string_list_split*()\n - string-list: unify string_list_split* functions\n - string-list: align string_list_split() with its _in_place() counterpart\n - string-list: report programming error with BUG\n (this branch is used by jc/strbuf-split.)\n\n string_list_split*() family of functions have been extended to\n simplify common use cases.\n\n Will merge to 'next'.\n source: <20250801220423.1230969-1-gitster@pobox.com>\n\n\n* am/xdiff-hash-tweak (2025-07-28) 3 commits\n - fixup! xdiff: optimize xdl_hash_record_verbatim\n - xdiff: optimize xdl_hash_record_verbatim\n - xdiff: refactor xdl_hash_record()\n\n Inspired by Ezekiel's recent effort to showcase Rust interface, the\n hash function implementation used to hash lines have been updated\n to the one used for ELF symbol lookup by Glibc.\n\n Comments?\n source: <20250728190520.10962-1-amonakov@ispras.ru>\n\n\n* ps/remote-rename-fix (2025-07-31) 7 commits\n (merged to 'next' on 2025-08-07 at 227d2faf29)\n + builtin/remote: only iterate through refs that are to be renamed\n + builtin/remote: rework how remote refs get renamed\n + builtin/remote: determine whether refs need renaming early on\n + builtin/remote: fix sign comparison warnings\n + refs: simplify logic when migrating reflog entries\n + refs: pass refname when invoking reflog entry callback\n + Merge branch 'ps/reflog-migrate-fixes' into ps/remote-rename-fix\n (this branch uses ps/reflog-migrate-fixes.)\n\n \"git remote rename origin upstream\" failed to move origin/HEAD to\n upstream/HEAD when origin/HEAD is unborn and performed other\n renames extremely inefficiently, which has been corrected.\n\n Will cook in 'next'.\n source: <20250731-pks-remote-rename-improvements-v2-0-dda6f083674d@pks.im>\n\n\n* ag/send-email-imap-sent (2025-07-23) 2 commits\n - send-email: enable copying emails to IMAP folder without actually sending them\n - send-email: add ability to send a copy of sent emails to an IMAP folder\n\n \"git send-email\" learned to drive \"git imap-send\" to store already\n sent e-mails in an IMAP folder.\n\n Comments?\n source: \n\n\n* en/ort-rename-fixes (2025-08-06) 7 commits\n - merge-ort: fix directory rename on top of source of other rename/delete\n - merge-ort: fix incorrect file handling\n - merge-ort: clarify the interning of strings in opt->priv->path\n - t6423: fix missed staging of file in testcases 12i,12j,12k\n - t6423: document two bugs with rename-to-self testcases\n - merge-ort: drop unnecessary temporary in check_for_directory_rename()\n - merge-ort: update comments to modern testfile location\n\n Various bugs about rename handling in \"ort\" merge strategy have\n been fixed.\n\n Will merge to 'next'?\n source: \n\n\n* ps/reflog-migrate-fixes (2025-08-05) 9 commits\n (merged to 'next' on 2025-08-07 at 8068e2ad68)\n + refs: fix invalid old object IDs when migrating reflogs\n + refs: stop unsetting REF_HAVE_OLD for log-only updates\n + refs/files: detect race when generating reflog entry for HEAD\n + refs: fix identity for migrated reflogs\n + ident: fix type of string length parameter\n + builtin/reflog: implement subcommand to write new entries\n + refs: export `ref_transaction_update_reflog()`\n + builtin/reflog: improve grouping of subcommands\n + Documentation/git-reflog: convert to use synopsis type\n (this branch is used by ps/remote-rename-fix.)\n\n \"git refs migrate\" to migrate the reflog entries from a refs\n backend to another had a handful of bugs squashed.\n\n Will cook in 'next'.\n source: <20250806-pks-reflog-append-v6-0-a50839653766@pks.im>\n\n\n* ds/sparse-checkout-clean (2025-07-16) 9 commits\n - sparse-checkout: make 'clean' clear more files\n - t: expand tests around sparse merges and clean\n - sparse-index: point users to new 'clean' action\n - sparse-checkout: add --verbose option to 'clean'\n - dir: add generic \"walk all files\" helper\n - sparse-checkout: match some 'clean' behavior\n - sparse-checkout: add basics of 'clean' command\n - sparse-checkout: remove use of the_repository\n - Merge branch 'ac/deglobal-sparse-variables' into ds/sparse-checkout-clean\n (this branch uses ac/deglobal-sparse-variables.)\n\n \"git sparse-checkout\" subcommand learned a new \"clean\" action to\n prune otherwise unused working-tree files that are outside the\n areas of interest.\n\n Needs to wait for the base topic to solidify.\n source: \n\n\n* pw/3.0-commentchar-auto-deprecation (2025-07-31) 4 commits\n - commit: print advice when core.commentString=auto\n - config: warn on core.commentString=auto\n - breaking-changes: deprecate support for core.commentString=auto\n - Merge branch 'ps/config-wo-the-repository' into pw/3.0-commentchar-auto-deprecation\n\n Proposes to deprecate \"core.commentChar=auto\" that attempts to\n dynamically pick a suitable comment character, as it is too much\n trouble to support for little benefit.\n\n Comments?\n source: \n\n\n* ua/t1517-short-help-tests (2025-08-07) 3 commits\n - t5304: move `prune -h` test from t1517\n - t5200: move `update-server-info -h` test from t1517\n - t/t1517: automate `git subcmd -h` tests outside a repository\n (this branch is used by dk/help-all.)\n\n Test shuffling.\n\n Will merge to 'next'.\n source: <20250808010651.591906-1-usmanakinyemi202@gmail.com>\n\n\n* tc/last-modified (2025-08-05) 4 commits\n - fixup! last-modified: new subcommand to show when files were last modified\n - last-modified: use Bloom filters when available\n - t/perf: add last-modified perf script\n - last-modified: new subcommand to show when files were last modified\n\n A new command \"git last-modified\" is proposed to show the closest\n ancestor commit that touched each path.\n source: <20250730175510.987383-1-toon@iotcl.com>\n\n\n* lo/repo-info (2025-08-07) 5 commits\n - repo: add the --format flag\n - repo: add the field layout.shallow\n - repo: add the field layout.bare\n - repo: add the field references.format\n - repo: declare the repo command\n\n A new subcommand \"git repo\" gives users a way to grab various\n repository characteristics.\n\n Will merge to 'next'.\n source: <20250807150239.6987-1-lucasseikioshiro@gmail.com>\n\n\n* ac/deglobal-sparse-variables (2025-07-18) 3 commits\n - environment: remove the global variable 'sparse_expect_files_outside_of_patterns'\n - environment: move access to \"core.sparsecheckoutcone\" into repo_settings\n - environment: move access to \"core.sparsecheckout\" into repo_settings\n (this branch is used by ds/sparse-checkout-clean.)\n\n Two global variables related to sparse checkout have been moved to\n the repository settings structure.\n\n Expecting a reroll.\n cf. \n source: \n\n\n* tb/prepare-midx-pack-cleanup (2025-05-28) 5 commits\n - midx: return a `packed_git` pointer from `prepare_midx_pack()`\n - midx-write.c: extract inner loop from fill_packs_from_midx()\n - midx-write.c: guard against incremental MIDXs in want_included_pack()\n - midx: access pack names through `nth_midxed_pack_name()`\n - Merge branch 'ps/midx-negative-packfile-cache' into tb/prepare-midx-pack-cleanup\n\n Improvement on Multi-pack-index API.\n\n Expecting a reroll.\n cf. <20250530065034.GC1321283@coredump.intra.peff.net>\n source: \n\n\n* cc/promisor-remote-capability (2025-07-31) 5 commits\n - promisor-remote: use string constants for 'name' and 'url' too\n - promisor-remote: allow a client to check fields\n - promisor-remote: refactor how we parse advertised fields\n - promisor-remote: allow a server to advertise more fields\n - promisor-remote: refactor to get rid of 'struct strvec'\n\n The \"promisor-remote\" capability mechanism has been updated to\n allow the \"partialCloneFilter\" settings and the \"token\" value to be\n communicated from the server side.\n\n Expecting a reroll.\n source: <20250731072401.3817074-1-christian.couder@gmail.com>\n"},{"id":"523907","messageId":"CAPig+cSbMeQ9yxXLFco8uH2kD84mDCu57sMZs5LtfMRnoKaYjw@mail.gmail.com","threadId":"63933","inReplyTo":"xmqqectl6unf.fsf@gitster.g","subject":"Re: What's cooking in git.git (Aug 2025, #03; Fri, 8)","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2025-08-11T05:50:40Z","receivedAt":"2025-08-11T05:50:52Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Fri, Aug 8, 2025 at 11:28 PM Junio C Hamano wrote:\n> * lo/repo-info (2025-08-07) 5 commits\n> - repo: add the --format flag\n> - repo: add the field layout.shallow\n> - repo: add the field layout.bare\n> - repo: add the field references.format\n> - repo: declare the repo command\n>\n> A new subcommand \"git repo\" gives users a way to grab various\n> repository characteristics.\n>\n> Will merge to 'next'.\n> source: <20250807150239.6987-1-lucasseikioshiro@gmail.com>\n\nI think this topic may deserve one more reroll before being merged to\n'next' since two or three comments from my previous review were not\nfully addressed[*]. (I also identified several nits in the latest\nversion but they need not hold up the topic.)\n\n[*]: https://lore.kernel.org/git/CAPig+cTA=UKbHd+BdCQUdTjvz1AzCNHi2XTREPhfUJfz_2Ny_A@mail.gmail.com/\n"},{"id":"523952","messageId":"xmqqbjol50io.fsf@gitster.g","threadId":"63933","inReplyTo":"CAPig+cSbMeQ9yxXLFco8uH2kD84mDCu57sMZs5LtfMRnoKaYjw@mail.gmail.com","subject":"Re: What's cooking in git.git (Aug 2025, #03; Fri, 8)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-08-11T15:41:19Z","receivedAt":"2025-08-11T15:41:22Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Eric Sunshine writes:\n\n> On Fri, Aug 8, 2025 at 11:28 PM Junio C Hamano wrote:\n>> * lo/repo-info (2025-08-07) 5 commits\n>> - repo: add the --format flag\n>> - repo: add the field layout.shallow\n>> - repo: add the field layout.bare\n>> - repo: add the field references.format\n>> - repo: declare the repo command\n>>\n>> A new subcommand \"git repo\" gives users a way to grab various\n>> repository characteristics.\n>>\n>> Will merge to 'next'.\n>> source: <20250807150239.6987-1-lucasseikioshiro@gmail.com>\n>\n> I think this topic may deserve one more reroll before being merged to\n> 'next' since two or three comments from my previous review were not\n> fully addressed[*]. (I also identified several nits in the latest\n> version but they need not hold up the topic.)\n\nThanks for stopping me.\n"}]}