{"thread":{"id":"63755","subject":"What's cooking in git.git (Jul 2025, #02; Mon, 7)","startedAt":"2025-07-08T00:11:15Z","lastAt":"2025-07-10T15:30:34Z","messageCount":17,"participants":["Junio C Hamano","Ayush Chandekar","René Scharfe","Carlo Marcelo Arenas Belón","Phillip Wood","Taylor Blau","Johannes Sixt","brian m. carlson","Elijah Newren"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"521486","messageId":"xmqqplebzgm7.fsf@gitster.g","threadId":"63755","inReplyTo":null,"subject":"What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-07-08T00:11:12Z","receivedAt":"2025-07-08T00:11:15Z","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\nSince Git 2.50 was tagged, it seems that number of old topics that\nare expecting a reroll has not shrunk. We may want to do something\nabout older ones.\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* ag/imap-send-resurrection (2025-06-19) 10 commits\n (merged to 'next' on 2025-06-23 at 7c2003159b)\n + imap-send: fix minor mistakes in the logs\n + imap-send: display the destination mailbox when sending a message\n + imap-send: display port alongwith host when git credential is invoked\n + imap-send: add ability to list the available folders\n + imap-send: enable specifying the folder using the command line\n + imap-send: add PLAIN authentication method to OpenSSL\n + imap-send: add support for OAuth2.0 authentication\n + imap-send: gracefully fail if CRAM-MD5 authentication is requested without OpenSSL\n + imap-send: fix memory leak in case auth_cram_md5 fails\n + imap-send: fix bug causing cfg->folder being set to NULL\n (this branch is used by jt/imap-send-message-fix.)\n\n \"git imap-send\" has been broken for a long time, which has been\n resurrected and then taught to talk OAuth2.0 etc.\n source: \n\n\n* cb/ci-freebsd-update-to-14.3 (2025-06-30) 1 commit\n (merged to 'next' on 2025-07-02 at def60da09b)\n + ci: update FreeBSD image to 14.3\n\n CI updates.\n source: \n\n\n* cb/daemon-fd-check-fix (2025-06-26) 1 commit\n (merged to 'next' on 2025-06-30 at 7a88e3eff9)\n + daemon: remove unnecesary restriction for listener fd\n\n Remove unnecessary check from \"git daemon\" code.\n source: <20250626095139.70751-1-carenas@gmail.com>\n\n\n* cb/daemon-retry-interrupted-accept (2025-06-27) 1 commit\n (merged to 'next' on 2025-07-02 at 8ad80bb873)\n + daemon: correctly handle soft accept() errors in service_loop\n\n When \"git daemon\" sees a signal while attempting to accept() a new\n client, instead of retrying, it skipped it by mistake, which has\n been corrected.\n cf. \n source: <20250627231404.27100-1-carenas@gmail.com>\n\n\n* jj/doc-branch-markup-fix (2025-06-29) 1 commit\n (merged to 'next' on 2025-07-02 at a83386e565)\n + doc: improve formatting in branch section\n\n Doc markup fix.\n source: <20250629190445.10185-1-kuba@kubajecminek.cz>\n\n\n* jk/fix-leak-send-pack (2025-07-01) 2 commits\n (merged to 'next' on 2025-07-02 at 666bd0f1ca)\n + send-pack: clean-up even when taking an early exit\n + send-pack: clean up extra_have oid array\n\n Leakfix.\n source: <20250627-jk-fix-leak-send-pack-v1-1-aadcf0ed8a4b@gmail.com>\n\n\n* jk/submodule-remote-lookup-cleanup (2025-06-23) 7 commits\n (merged to 'next' on 2025-06-24 at 0354a7779f)\n + submodule: look up remotes by URL first\n + submodule: move get_default_remote_submodule()\n + submodule--helper: improve logic for fallback remote name\n + remote: remove the_repository from some functions\n + dir: move starts_with_dot(_dot)_slash to dir.h\n + remote: fix tear down of struct remote\n + remote: remove branch->merge_name and fix branch_release()\n\n Updating submodules from the upstream did not work well when\n submodule's HEAD is detached, which has been improved.\n source: <20250623-jk-submodule-helper-use-url-v4-0-133ef3d89569@gmail.com>\n\n\n* jt/imap-send-message-fix (2025-06-20) 3 commits\n (merged to 'next' on 2025-06-24 at 106e5c22eb)\n + imap-send: improve error messages with configuration hints\n + imap-send: fix confusing 'store' terminology in error message\n + Merge branch 'ag/imap-send-resurrection' into jt/imap-send-message-fix\n (this branch uses ag/imap-send-resurrection.)\n\n Update some error messages from \"git imap-send\".\n source: <20250620155614.901816-1-joerg@thalheim.io>\n\n\n* ps/contrib-sweep (2025-05-12) 11 commits\n (merged to 'next' on 2025-06-24 at 5d97a089a8)\n + contrib: remove some scripts in \"stats\" directory\n + contrib: remove \"git-new-workdir\"\n + contrib: remove \"emacs\" directory\n + contrib: remove \"git-resurrect.sh\"\n + contrib: remove \"persistent-https\" remote helper\n + contrib: remove \"mw-to-git\"\n + contrib: remove \"hooks\" directory\n + contrib: remove \"thunderbird-patch-inline\"\n + contrib: remove remote-helper stubs\n + contrib: remove \"examples\" directory\n + contrib: remove \"remotes2config.sh\"\n\n Remove bunch of stuff from contrib/ hierarchy.\n source: <20250512-pks-contrib-spring-cleanup-v3-0-32e151b0bfb0@pks.im>\n\n--------------------------------------------------\n[New Topics]\n\n* bs/remote-helpers-doc-markup-fix (2025-07-02) 1 commit\n (merged to 'next' on 2025-07-07 at 60c2a47d1b)\n + gitremote-helpers.adoc: fix formatting\n\n Docfix.\n\n Will merge to 'master'.\n source: <20250702161951.22908-2-bacs@librecast.net>\n\n\n* cb/total-ram-bsd-fix (2025-07-07) 1 commit\n (merged to 'next' on 2025-07-07 at d9a7ca747c)\n + builtin/gc: correct total_ram calculation with HAVE_BSD_SYSCTL\n\n Use of sysctl() system call to learn the total RAM size used on\n BSDs has been corrected.\n\n Will merge to 'master'.\n source: <20250707164518.6600-1-carenas@gmail.com>\n\n\n* ps/use-reftable-as-default-in-3.0 (2025-07-04) 2 commits\n - setup: use \"reftable\" format when experimental features are enabled\n - BreakingChanges: announce switch to \"reftable\" format\n\n The reftable ref backend has matured enough; Git 3.0 will make it\n the default format in a newly created repositories by default.\n\n Will merge to 'next'.\n source: <20250704-pks-reftable-default-backend-v3-0-a1eb63e8442a@pks.im>\n\n\n* hy/read-cache-lock-error-fix (2025-07-03) 1 commit\n - read-cache: report lock error when refreshing index\n\n A failure to open the index file for writing due to conflicting\n access did not state what went wrong, which has been corrected.\n\n Will merge to 'next'.\n source: <20250703074502.45593-1-hanyang.tony@bytedance.com>\n\n\n* jk/all-negative-diff-filter-fix (2025-07-03) 1 commit\n (merged to 'next' on 2025-07-07 at 139dd3db75)\n + setup_revisions(): turn on diffs for all-negative diff filter\n\n A diff-filter with negative-only specification like \"git log\n --diff-filter=d\" did not trigger correctly, which has been fixed.\n\n Will merge to 'master'.\n source: <20250703224428.GB1909836@coredump.intra.peff.net>\n\n\n* jk/remote-avoid-overlapping-names (2025-07-05) 1 commit\n - remote: detect collisions in remote names\n\n \"git remote\" now detects remote names that overlap with each other\n (e.g., remote nickname \"outer\" and \"outer/inner\" are used at the\n same time), as it will lead to overlapping remote-tracking\n branches.\n\n Will merge to 'next'?\n source: <20250705185842.GA2496172@coredump.intra.peff.net>\n\n\n* ps/meson-cleanups (2025-07-03) 8 commits\n - ci: use Meson's new `--slice` option\n - meson: update subproject wrappers\n - meson: fix GIT_EXEC_PATH with overridden -Dlibexecdir=\n - meson: fix lookup of shell on MINGW64\n - meson: clean up unnecessary variables\n - meson: improve summary of auto-detected features\n - meson: stop printing 'https' option twice in our summaries\n - meson: stop discovering native version of Python\n\n Meson-based build update.\n\n Breaks Windows CI job at GitHub.\n source: <20250703-b4-pks-meson-cleanups-v1-0-2804c2932abe@pks.im>\n\n\n* ps/perlless-test-fixes (2025-07-07) 2 commits\n - t5333: fix missing terminator for sed(1) 's' command\n - t4150: fix warning printed by awk due to escaped '\\@'\n\n Test fixes.\n\n Will merge to 'next'.\n source: <20250707-b4-pks-t-perlless-fixes-v1-0-92b2de1c3dd0@pks.im>\n\n\n* re/ssh-sign-buffer-fix (2025-07-07) 1 commit\n - ssh signing: don't detach the filename strbuf from key_file tempfile\n\n Tempfile removal fix in the codepath to sign commits with SSH keys.\n\n Will merge to 'next'.\n source: <20250707184852.16010-1-redoste@redoste.xyz>\n\n\n* rj/freebsd-sysinfo-build-fix (2025-07-04) 1 commit\n - build: fix FreeBSD build when sysinfo compat library installed\n\n Build fix for FreeBSD.\n\n Will merge to 'next'.\n source: \n\n\n* rp/apply-intent-to-add-fix (2025-07-07) 4 commits\n - apply docs: clarify wording for --intent-to-add\n - t4140: test apply --intent-to-add interactions\n - apply: only write intents to add for new files\n - apply: read in the index in --intent-to-add mode\n\n \"git apply -N\" should start from the current index and register\n only new files, but it instead started from an empty index, which\n has been corrected.\n\n Will merge to 'next'.\n source: <20250707121534.2933349-1-ray@ameretat.dev>\n\n\n* ts/merge-orig-head-doc-fix (2025-07-05) 1 commit\n - docs: correct ORIG_HEAD example in \"git merge\" documentation\n\n Doc fix.\n\n Will merge to 'next'.\n source: \n\n\n* ua/t1517-short-help-tests (2025-07-06) 7 commits\n - t/t1517: move verify-tag -h test to t1517\n - t/t1517: move verify-commit -h test to t1517\n - t/t1517: move send-pack -h test to t1517\n - t/t1517: move pack-refs -h test to t1517\n - t/t1517: move ls-files -h test to t1517\n - t/t1517: move for-each-ref -h test to t1517\n - t/t1517: move checkout-index -h test to t1517\n\n Test shuffling.\n\n Comments?\n source: <20250706215039.715732-1-usmanakinyemi202@gmail.com>\n\n--------------------------------------------------\n[Cooking]\n\n* ac/prune-wo-the-repository (2025-07-04) 2 commits\n (merged to 'next' on 2025-07-07 at 3dd296a911)\n + builtin/prune: stop depending on 'the_repository'\n + repository: move 'repository_format_precious_objects' to repo scope\n\n Some code paths in the \"git prune\" used to ignore passed in\n repository object and used the_repository singleton instance\n instead, which has been corrected.\n\n Will merge to 'master'.\n source: \n\n\n* ag/doc-send-email (2025-06-30) 5 commits\n - docs: mention possible options for Proton Mail users\n - docs: add a paragraph explaining the `sendmailCmd` option of sendemail\n - docs: add an OAuth2.0 credential helper for AOL accounts\n - docs: add outlookidfix config option to sendemail documentation\n - docs: link OpenSSL's verify(1) manual page to know about -CAfile and -CApath options\n\n Documentation updates for \"git send-email\".\n\n Will merge to 'next'?\n source: <20250630180511.499-1-gargaditya08@proton.me>\n\n\n* rs/parse-options-precision (2025-06-29) 6 commits\n - parse-options: add precision handling for OPTION_COUNTUP\n - parse-options: add precision handling for OPTION_BITOP\n - parse-options: add precision handling for OPTION_NEGBIT\n - parse-options: add precision handling for OPTION_BIT\n - parse-options: add precision handling for OPTION_SET_INT\n - parse-options: add precision handling for PARSE_OPT_CMDMODE\n\n Define .precision to more canned parse-options type to avoid bugs\n coming from using a variable with a wrong type to capture the\n parsed values.\n\n Will merge to 'next'?\n source: \n\n\n* kh/doc-config-subcommands (2025-07-01) 5 commits\n - config: mention --url in the synopsis\n - config: use --value instead of value-pattern\n - config: document --[no-]value\n - config: use --value= consistently\n - config: document --[no-]show-names\n\n Documentation updates.\n\n Will merge to 'next'.\n source: \n\n\n* kn/for-each-ref-skip (2025-07-04) 4 commits\n - for-each-ref: introduce a '--skip-until' option\n - refs: selectively set prefix in the seek functions\n - ref-cache: remove unused function 'find_ref_entry()'\n - refs: expose `ref_iterator` via 'refs.h'\n\n \"git for-each-ref\" learns \"--skip-until\" option to help\n applications that want to page its output.\n\n Expecting a reroll.\n cf. \n source: <20250704-306-git-for-each-ref-pagination-v2-0-bcde14acdd81@gmail.com>\n\n\n* tc/last-modified (2025-07-01) 5 commits\n . (style) fix bad changes suggested by clang-format\n . (style) clang-format suggested changes\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\n Breaks check-docs.\n source: <20250630-toon-new-blame-tree-v3-0-3516025dc3bc@iotcl.com>\n\n\n* cb/daemon-reap-children (2025-06-26) 4 commits\n - daemon: explicitly allow EINTR during poll()\n - daemon: use sigaction() to install child_handler()\n - compat/mingw: allow sigaction(SIGCHLD)\n - compat/posix.h: track SA_RESTART fallback\n\n Futz with SIGCHLD handling in \"git daemon\".\n\n Stalled?\n cf. \n source: \n\n\n* ac/auto-comment-char-fix (2025-06-30) 1 commit\n - commit: avoid scanning trailing comments when 'core.commentChar' is \"auto\"\n\n \"git commit\" that concludes a conflicted merge failed to notice and remove\n existing comment added automatically (like \"# Conflicts:\") when the\n core.commentstring is set to 'auto'.\n\n Expecting a reroll.\n cf. \n source: <20250630182527.69167-1-ayu.chandekar@gmail.com>\n\n\n* kn/clang-format-updates (2025-07-02) 3 commits\n - meson: add rule to run 'git clang-format'\n - clang-format: add 'RemoveBracesLLVM' to the main config\n - clang-format: set 'ColumnLimit' to 0\n\n Update \".clang-format\" and \".editorconfig\" to match our style guide\n a bit better.\n\n Will merge to 'next'.\n source: <20250702-525-make-clang-format-more-robust-v3-0-705344f30580@gmail.com>\n\n\n* ly/changed-paths-traversal (2025-07-04) 4 commits\n - bloom: optimize multiple pathspec items in revision traversal\n - bloom: replace struct bloom_key * with struct bloom_keyvec\n - bloom: rename function operates on bloom_key\n - bloom: add test helper to return murmur3 hash\n\n Lift the limitation to use changed-path filter in \"git log\" so that\n it can be used for a pathspec with multiple literal paths.\n\n Expecting a reroll.\n cf. <5DB7714D-4009-47C4-A8F7-1C375C6D29AF@smail.nju.edu.cn>\n source: <20250704111437.2660251-1-502024330056@smail.nju.edu.cn>\n\n\n* mc/netrc-service-names (2025-06-25) 3 commits\n - contrib: better support symbolic port names in git-credential-netrc\n - contrib: warn for invalid netrc file ports in git-credential-netrc\n - contrib: use a more portable shebang for git-credential-netrc\n\n \"netrc\" credential helper has been improved to understand textual\n service names (like smtp) in addition to the numeric port numbers\n (like 25).\n\n Will merge to 'next'.\n source: <20250625142511.28857-1-maxim@guixotic.coop>\n\n\n* ph/fetch-prune-optim (2025-07-01) 3 commits\n - clean up interface for refs_warn_dangling_symrefs\n - refs: remove old refs_warn_dangling_symref\n - fetch-prune: optimize dangling-ref reporting\n\n \"git fetch --prune\" used to be O(n^2) expensive when there are many\n refs, which has been corrected.\n\n What's the status of this one?\n cf. \n source: <20250702011214.2835529-2-phil.hord@gmail.com>\n\n\n* bc/use-sha256-by-default-in-3.0 (2025-07-01) 11 commits\n - Enable SHA-256 by default in breaking changes mode\n - help: add a build option for default hash\n - t5300: choose the built-in hash outside of a repo\n - t4042: choose the built-in hash outside of a repo\n - t1007: choose the built-in hash outside of a repo\n - t: default to compile-time default hash if not set\n - setup: use the default algorithm to initialize repo format\n - Use legacy hash for legacy formats\n - builtin: use default hash when outside a repository\n - hash: add a constant for the legacy hash algorithm\n - hash: add a constant for the default hash algorithm\n\n Prepare to flip the default hash function to SHA-256.\n\n Will merge to 'next'?\n source: <20250701212237.766774-1-sandals@crustytoothpaste.net>\n\n\n* jc/coccicheck-fails-make-when-it-fails (2025-06-23) 1 commit\n - coccicheck: fail \"make\" when it fails\n\n \"make coccicheck\" succeeds even when spatch made suggestions, which\n has been updated to fail in such a case.\n\n Will merge to 'next'.\n source: \n\n\n* lo/repo-info (2025-06-19) 7 commits\n . repo-info: add field layout.shallow\n . repo-info: add field layout.bare\n . repo-info: add the field references.format\n . repo-info: add the --allow-empty flag\n . repo-info: add plaintext as an output format\n . repo-info: add the --format flag\n . repo-info: declare the repo-info command\n\n A new subcommand \"git repo-info\" gives users a way to grab various\n repository characteristics.\n\n Expecting a reroll, if only to fix \"make check-docs\".\n source: <20250619225751.99699-1-lucasseikioshiro@gmail.com>\n\n\n* cc/fast-import-export-signature-names (2025-06-19) 1 commit\n - fast-(import|export): improve on commit signature output format\n\n Clean up the way how signature on commit objects are exported to\n and imported from fast-import stream.\n\n Stalled?\n cf. \n source: <20250619133630.727274-1-christian.couder@gmail.com>\n\n\n* ac/deglobal-sparse-variables (2025-06-30) 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\n Two global variables related to sparse checkout have been moved to\n the repository settings structure.\n\n Breaks end-user facing behaviour?\n cf. <17b7f51c-0c3d-4d63-a501-47ce829f7345@gmail.com>\n source: \n\n\n* ow/rebase-verify-insn-fmt-before-initializing-state (2025-06-09) 1 commit\n - rebase: write script before initializing state\n\n \"git rebase -i\" with bogus rebase.instructionFormat configuration\n failed to produce the todo file after recording the state files,\n leading to confused \"git status\"; this has been corrected.\n\n Expecting a reroll.\n cf. <7e796844-97e2-4b45-a76e-4c1fcb1da3ae@gmail.com>\n source: <20250609221055.136074-1-oystwa@gmail.com>\n\n\n* bs/config-mak-freebsd (2025-07-02) 2 commits\n (merged to 'next' on 2025-07-07 at d6761aa225)\n + build: retire NO_UINTMAX_T\n + config.mak.uname: set NO_MEMMEM only for functional version\n\n Drop FreeBSD 4 support and assume we are at least at FreeBSD 6 with\n memmem() supported.\n\n Will merge to 'master'.\n source: <20250702093736.36074-1-carenas@gmail.com>\n\n\n* jc/tag-idempotent-no-op (2025-06-10) 1 commit\n - tag: allow idempotent \"git tag\" without \"--force\"\n\n \"git tag T O\" when the tag T is already pointing at the object O is\n a no-op; we used to but no longer error out such a request and\n require \"--force\" and instead turn it into a no-op.\n\n Will discard.\n cf. \n source: \n\n\n* ss/compat-bswap-revamp (2025-06-11) 6 commits\n - bswap.h: provide a built-in based version of bswap32/64 if possible\n - bswap.h: remove optimized x86 version of bswap32/64\n - bswap.h: always overwrite ntohl/ntohll macros\n - bswap.h: define GIT_LITTLE_ENDIAN on MSVC as little endian\n - bswap.h: add support for __BYTE_ORDER__\n - Merge branch 'ss/revert-builtin-bswap-stuff' into ss/compat-bswap-revamp\n\n Clean-up compat/bswap.h mess.\n\n Stalled.\n cf. \n source: <20250611221444.1567638-1-sebastian@breakpoint.cc>\n\n\n* ja/doc-git-log-markup (2025-07-07) 9 commits\n - doc: git-log: convert log config to new doc format\n - doc: git-log: convert diff options to new doc format\n - doc: git-log: convert pretty formats to new doc format\n - doc: git-log: convert pretty options to new doc format\n - doc: git-log: convert rev list options to new doc format\n - doc: git-log: convert line range format to new doc format\n - doc: git-log: convert line range options to new doc format\n - doc: git-log convert rev-list-description to new doc format\n - doc: convert git-log to new documentation format\n\n Doc mark-up updates.\n\n Will merge to 'next'?\n source: \n\n\n* sk/reftable-clarify-tests (2025-06-05) 10 commits\n - t/unit-tests: finalize migration of reftable-related tests\n - t/unit-tests: convert reftable stack test to use clar\n - t/unit-tests: convert reftable record test to use clar\n - t/unit-tests: convert reftable readwrite test to use clar\n - t/unit-tests: convert reftable table test to use clar\n - t/unit-tests: convert reftable pq test to use clar\n - t/unit-tests: convert reftable merged test to use clar\n - t/unit-tests: convert reftable block test to use clar\n - t/unit-tests: convert reftable basics test to use clar test framework\n - t/unit-tests: implement clar specific reftable test helper functions\n\n The reftable unit tests are now ported to the \"clar\" unit testing\n framework.\n\n Expecting a reroll.\n cf. \n source: <20250605140644.239199-1-kuforiji98@gmail.com>\n\n\n* ly/load-bitmap-leakfix (2025-06-30) 3 commits\n - pack-bitmap: add load corrupt bitmap test\n - pack-bitmap: reword comments in test_bitmap_commits()\n - pack-bitmap: fix memory leak if load_bitmap() failed\n\n Leakfix with a new and a bit invasive test.\n\n What's the status of this one?\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* kn/fetch-push-bulk-ref-update (2025-06-20) 6 commits\n (merged to 'next' on 2025-07-02 at db06df3871)\n + receive-pack: handle reference deletions separately\n + refs/files: skip updates with errors in batched updates\n + receive-pack: use batched reference updates\n + send-pack: fix memory leak around duplicate refs\n + fetch: use batched reference updates\n + refs: add function to translate errors to strings\n\n \"git push\" and \"git fetch\" are taught to update refs in batches to\n gain performance.\n\n Will merge to 'master'.\n source: <20250519-501-update-git-fetch-1-to-use-partial-transactions-v3-0-6cdfd4f769b9@gmail.com>\n source: <20250620-6769-address-test-failures-in-the-next-branch-caused-by-batched-reference-updates-v5-0-f35ee6b59a82@gmail.com>\n\n\n* kj/renamed-submodule (2025-06-07) 2 commits\n - submodule: skip redundant active entries when pattern covers path\n - submodule: prevent overwriting .gitmodules entry 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\n What's the status of this one?\n cf. \n source: <20250608032705.11990-1-jayatheerthkulkarni2005@gmail.com>\n\n\n* lm/add-p-context (2025-06-28) 4 commits\n - add-patch: add diff.context command line overrides\n - add-patch: respect diff.context configuration\n - test: use \"test_config\"\n - test: use \"test_grep\"\n\n \"git add/etc -p\" now honors diff.context configuration variable,\n and learns to honor -U option.\n\n Will merge to 'next'?\n source: \n\n\n* ps/object-store (2025-07-01) 17 commits\n - odb: rename `read_object_with_reference()`\n - odb: rename `pretend_object_file()`\n - odb: rename `has_object()`\n - odb: rename `repo_read_object_file()`\n - odb: rename `oid_object_info()`\n - odb: trivial refactorings to get rid of `the_repository`\n - odb: get rid of `the_repository` when handling submodule sources\n - odb: get rid of `the_repository` when handling the primary source\n - odb: get rid of `the_repository` in `for_each()` functions\n - odb: get rid of `the_repository` when handling alternates\n - odb: get rid of `the_repository` in `odb_mkstemp()`\n - odb: get rid of `the_repository` in `assert_oid_type()`\n - odb: get rid of `the_repository` in `find_odb()`\n - odb: introduce parent pointers\n - object-store: rename files to \"odb.{c,h}\"\n - object-store: rename `object_directory` to `odb_source`\n - object-store: rename `raw_object_store` to `object_database`\n\n Code clean-up around object access API.\n\n Will merge to 'next'.\n source: <20250701-pks-object-store-wo-the-repository-v6-0-dbf3894ab4e2@pks.im>\n\n\n* cc/promisor-remote-capability (2025-06-25) 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 What's the status of this one?\n cf. \n source: <20250625125055.1375596-1-christian.couder@gmail.com>\n\n\n* sj/string-list (2025-06-28) 8 commits\n - u-string-list: move \"remove duplicates\" test to \"u-string-list.c\"\n - u-string-list: move \"filter string\" test to \"u-string-list.c\"\n - u-string-list: move \"test_split_in_place\" to \"u-string-list.c\"\n - u-string-list: move \"test_split\" into \"u-string-list.c\"\n - string-list: enable sign compare warnings check\n - string-list: return index directly when inserting an existing element\n - string-list: remove unused \"insert_at\" parameter from add_entry\n - string-list: fix sign compare warnings for loop iterator\n\n Code and test clean-up around string-list API.\n\n Will merge to 'next'.\n source: \n\n\n* tb/midx-avoid-cruft-packs (2025-06-23) 9 commits\n - repack: exclude cruft pack(s) from the MIDX where possible\n - pack-objects: introduce '--stdin-packs=follow'\n - pack-objects: swap 'show_{object,commit}_pack_hint'\n - pack-objects: fix typo in 'show_object_pack_hint()'\n - pack-objects: perform name-hash traversal for unpacked objects\n - pack-objects: declare 'rev_info' for '--stdin-packs' earlier\n - pack-objects: factor out handling '--stdin-packs'\n - pack-objects: limit scope in 'add_object_entry_from_pack()'\n - pack-objects: use standard option incompatibility functions\n\n \"pack-objects\" has been taught to avoid pointing into objects in\n cruft packs from midx.\n\n Will merge to 'next'?\n source: \n\n--------------------------------------------------\n[Discarded]\n\n* kn/fetch-push-bulk-ref-update-fixup (2025-06-20) 7 commits\n . receive-pack: handle reference deletions separately\n . refs/files: skip updates with errors in batched updates\n . Merge branch 'kn/fetch-push-bulk-ref-update' into kn/fetch-push-bulk-ref-update-fixup\n\n Follow-up fixes to the base topic.\n\n Superseded--folded into the base topic.\n source: <20250620-6769-address-test-failures-in-the-next-branch-caused-by-batched-reference-updates-v5-0-f35ee6b59a82@gmail.com>\n\n\n* jc/cocci-dtype (2025-06-18) 1 commit\n . cocci: do not directly access the .d_type member in struct dirent\n\n Catch direct access to .d_type member of struct dirent, as some\n non-POSIX compliant systems we support lack it, and rewrite to use\n DTYPE() macro, which is not quite the right thing to do.\n\n Would silently convert a broken code with code with another breakage.\n source: \n"},{"id":"521488","messageId":"CAE7as+YC9kP57hz+6TxuXq1c72mcvEdzwZ1Y3mNTTH5Dfh0mJQ@mail.gmail.com","threadId":"63755","inReplyTo":"xmqqplebzgm7.fsf@gitster.g","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Ayush Chandekar","fromEmail":"ayu.chandekar@gmail.com","sentAt":"2025-07-08T00:47:57Z","receivedAt":"2025-07-08T00:48:08Z","isPatch":false,"sender":{"key":"ayu.chandekar@gmail.com","avatar":"https://avatars.githubusercontent.com/u/137001939?v=4"},"body":"Hi Junio,\n\nOn Tue, Jul 8, 2025 at 5:44 AM Junio C Hamano wrote:\n>\n\n[snip]\n\n>\n> * ac/auto-comment-char-fix (2025-06-30) 1 commit\n> - commit: avoid scanning trailing comments when 'core.commentChar' is \"auto\"\n>\n> \"git commit\" that concludes a conflicted merge failed to notice and remove\n> existing comment added automatically (like \"# Conflicts:\") when the\n> core.commentstring is set to 'auto'.\n>\n> Expecting a reroll.\n> cf. \n> source: <20250630182527.69167-1-ayu.chandekar@gmail.com>\n>\n\nI sent an RFC related to this recently: [1]\nI will send an updated patch once I receive some feedback on it.\n\nThanks!\n\n[1]: https://lore.kernel.org/git/CAE7as+YXwesgk2tna4kEC34EbQ=-eA+thQBqU3qnveDh9rbt8g@mail.gmail.com/\n"},{"id":"521630","messageId":"861e6166-bda3-41c9-b259-2e46a77b6d84@web.de","threadId":"63755","inReplyTo":"xmqqplebzgm7.fsf@gitster.g","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"René Scharfe","fromEmail":"l.s.r@web.de","sentAt":"2025-07-09T09:25:55Z","receivedAt":"2025-07-09T09:31:13Z","isPatch":false,"sender":{"key":"l.s.r@web.de","avatar":"https://avatars.githubusercontent.com/u/26122331?v=4"},"body":"On 7/8/25 2:11 AM, Junio C Hamano wrote:\n> * rs/parse-options-precision (2025-06-29) 6 commits\n> - parse-options: add precision handling for OPTION_COUNTUP\n> - parse-options: add precision handling for OPTION_BITOP\n> - parse-options: add precision handling for OPTION_NEGBIT\n> - parse-options: add precision handling for OPTION_BIT\n> - parse-options: add precision handling for OPTION_SET_INT\n> - parse-options: add precision handling for PARSE_OPT_CMDMODE\n> \n> Define .precision to more canned parse-options type to avoid bugs\n> coming from using a variable with a wrong type to capture the\n> parsed values.\n> \n> Will merge to 'next'?\n> source: \nWill send v2 shortly.\n\nRené\n\n"},{"id":"521646","messageId":"vl7ahhcqgci3xemqhtdugdhar24ewl7mu4wqwxnc3jag5blpoo@l7b24mahadyi","threadId":"63755","inReplyTo":"xmqqplebzgm7.fsf@gitster.g","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Carlo Marcelo Arenas Belón","fromEmail":"carenas@gmail.com","sentAt":"2025-07-09T10:41:13Z","receivedAt":"2025-07-09T10:41:16Z","isPatch":false,"sender":{"key":"carenas@gmail.com","avatar":"https://avatars.githubusercontent.com/u/76036?v=4"},"body":"On Mon, Jul 07, 2025 at 05:11:12PM -0800, Junio C Hamano wrote:\n> \n> * cb/daemon-reap-children (2025-06-26) 4 commits\n> - daemon: explicitly allow EINTR during poll()\n> - daemon: use sigaction() to install child_handler()\n> - compat/mingw: allow sigaction(SIGCHLD)\n> - compat/posix.h: track SA_RESTART fallback\n> \n> Futz with SIGCHLD handling in \"git daemon\".\n> \n> Stalled?\n> cf. \n> source: \n\nI don't think so, but definitely missing reviews (specially for patch 2)\nand slightly controversial.\n\nI wasn't planning any further changes, and while I have some for the\n\"related\" patchset which enhances the notifications by using a self pipe\nwas holding them (as well as the related feedback) to allow for this to\nmature on its own.\n\nOn the rationale on why this is independently useful, note that we are\ncurrently relying in at least 2 \"unspecified\" behaviours:\n\n1) using signal() means that it is implementation defined if SA_RESTART\nwill be enabled or not for that signal, and\n2) if SA_RESTART is enabled, it is implementation defined if we might get\ninterrupted in poll().\n\nboth are resolved by using sigaction() instead, and it is up to us to\ndecide if SA_RESTART is enabled or not (which might make patch 4 obsolete\nif we decide against).\n\nCarlo\n\nCC: Johannes Sixt on feedback for SIGCHLD in mingw which uses 17 instead\n of 22 (cygwin and others) and therefore seem to cause signal to err\n without setting errno as it should.\n"},{"id":"521676","messageId":"299f547b-635d-4a2c-958e-7ef6200ea69c@gmail.com","threadId":"63755","inReplyTo":"vl7ahhcqgci3xemqhtdugdhar24ewl7mu4wqwxnc3jag5blpoo@l7b24mahadyi","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Phillip Wood","fromEmail":"phillip.wood123@gmail.com","sentAt":"2025-07-09T14:15:01Z","receivedAt":"2025-07-09T14:15:04Z","isPatch":false,"sender":{"key":"phillip.wood@dunelm.org.uk","avatar":null},"body":"On 09/07/2025 11:41, Carlo Marcelo Arenas Belón wrote:\n> On Mon, Jul 07, 2025 at 05:11:12PM -0800, Junio C Hamano wrote:\n>>\n>> * cb/daemon-reap-children (2025-06-26) 4 commits\n>> - daemon: explicitly allow EINTR during poll()\n>> - daemon: use sigaction() to install child_handler()\n>> - compat/mingw: allow sigaction(SIGCHLD)\n>> - compat/posix.h: track SA_RESTART fallback\n>>\n>> Futz with SIGCHLD handling in \"git daemon\".\n>>\n>> Stalled?\n>> cf. \n>> source: \n> \n> I don't think so, but definitely missing reviews (specially for patch 2)\n> and slightly controversial.\n> \n> I wasn't planning any further changes,\n\nI'd very much like to see a re-roll cf. \n\n\nThanks\n\nPhillip\n\n> and while I have some for the\n> \"related\" patchset which enhances the notifications by using a self pipe\n> was holding them (as well as the related feedback) to allow for this to\n> mature on its own.\n> \n> On the rationale on why this is independently useful, note that we are\n> currently relying in at least 2 \"unspecified\" behaviours:\n> \n> 1) using signal() means that it is implementation defined if SA_RESTART\n> will be enabled or not for that signal, and\n> 2) if SA_RESTART is enabled, it is implementation defined if we might get\n> interrupted in poll().\n> \n> both are resolved by using sigaction() instead, and it is up to us to\n> decide if SA_RESTART is enabled or not (which might make patch 4 obsolete\n> if we decide against).\n> \n> Carlo\n> \n> CC: Johannes Sixt on feedback for SIGCHLD in mingw which uses 17 instead\n> of 22 (cygwin and others) and therefore seem to cause signal to err\n> without setting errno as it should.\n> \n\n"},{"id":"521680","messageId":"aG6A19ZgxwpdJuow@nand.local","threadId":"63755","inReplyTo":"xmqqplebzgm7.fsf@gitster.g","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Taylor Blau","fromEmail":"me@ttaylorr.com","sentAt":"2025-07-09T14:46:47Z","receivedAt":"2025-07-09T14:46:57Z","isPatch":false,"sender":{"key":"me@ttaylorr.com","avatar":"https://avatars.githubusercontent.com/u/301000140?v=4"},"body":"> * tb/midx-avoid-cruft-packs (2025-06-23) 9 commits\n> - repack: exclude cruft pack(s) from the MIDX where possible\n> - pack-objects: introduce '--stdin-packs=follow'\n> - pack-objects: swap 'show_{object,commit}_pack_hint'\n> - pack-objects: fix typo in 'show_object_pack_hint()'\n> - pack-objects: perform name-hash traversal for unpacked objects\n> - pack-objects: declare 'rev_info' for '--stdin-packs' earlier\n> - pack-objects: factor out handling '--stdin-packs'\n> - pack-objects: limit scope in 'add_object_entry_from_pack()'\n> - pack-objects: use standard option incompatibility functions\n>\n> \"pack-objects\" has been taught to avoid pointing into objects in\n> cruft packs from midx.\n>\n> Will merge to 'next'?\n> source: \n\nI think that this one is ready to go. Since Elijah and Peff last\nreviewed it, it hasn't changed substantially (other than a few\nbugfix-related changes that were discovered while rolling this out at\nGitHub).\n\nThe series has been running on GitHub's production infrastructure for\nthe last month or two without issue, so I think this is good from a\nstability perspective.\n\nI've CC'd Elijah and Peff here, since they were the last two to review\nthe series, but I don't think that they have any objections to this\nmoving along.\n\nThanks,\nTaylor\n"},{"id":"521693","messageId":"xmqqy0sxnzo5.fsf@gitster.g","threadId":"63755","inReplyTo":"861e6166-bda3-41c9-b259-2e46a77b6d84@web.de","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-07-09T15:37:14Z","receivedAt":"2025-07-09T15:37:17Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"René Scharfe writes:\n\n> On 7/8/25 2:11 AM, Junio C Hamano wrote:\n>> * rs/parse-options-precision (2025-06-29) 6 commits\n>> - parse-options: add precision handling for OPTION_COUNTUP\n>> - parse-options: add precision handling for OPTION_BITOP\n>> - parse-options: add precision handling for OPTION_NEGBIT\n>> - parse-options: add precision handling for OPTION_BIT\n>> - parse-options: add precision handling for OPTION_SET_INT\n>> - parse-options: add precision handling for PARSE_OPT_CMDMODE\n>> \n>> Define .precision to more canned parse-options type to avoid bugs\n>> coming from using a variable with a wrong type to capture the\n>> parsed values.\n>> \n>> Will merge to 'next'?\n>> source: \n> Will send v2 shortly.\n\nThanks for stopping me.\n\n"},{"id":"521695","messageId":"668ce4d4-3b60-47e0-a4a5-dbf73efd1e75@kdbg.org","threadId":"63755","inReplyTo":"vl7ahhcqgci3xemqhtdugdhar24ewl7mu4wqwxnc3jag5blpoo@l7b24mahadyi","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Johannes Sixt","fromEmail":"j6t@kdbg.org","sentAt":"2025-07-09T15:04:51Z","receivedAt":"2025-07-09T15:43:57Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Am 09.07.25 um 12:41 schrieb Carlo Marcelo Arenas Belón:\n> CC: Johannes Sixt on feedback for SIGCHLD in mingw which uses 17 instead\n> of 22 (cygwin and others) and therefore seem to cause signal to err\n> without setting errno as it should.\n\nI don't know what the relevance of the actual number of a signal is.\nNobody is supposed to use the number, only the macro. But I may be\nmisjudging the situation as a bystander of this discussion.\n\nFurthermore, there is no such thing as \"a signal\" on Windows (outside of\nCygwin), let alone a SIGCHLD. Therefore, this topic about SA_RESTART is\nirrelevant for the MinGW port.\n\nThat said, we have a very stupid emulation of SIGALRM, but it doesn't\nwork like a POSIX signal in any way (if it works at all).\n\n-- Hannes\n\n"},{"id":"521703","messageId":"xmqqa55dnxe9.fsf@gitster.g","threadId":"63755","inReplyTo":"vl7ahhcqgci3xemqhtdugdhar24ewl7mu4wqwxnc3jag5blpoo@l7b24mahadyi","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-07-09T16:26:22Z","receivedAt":"2025-07-09T16:26:24Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Carlo Marcelo Arenas Belón writes:\n\n> On Mon, Jul 07, 2025 at 05:11:12PM -0800, Junio C Hamano wrote:\n>> \n>> * cb/daemon-reap-children (2025-06-26) 4 commits\n>> - daemon: explicitly allow EINTR during poll()\n>> - daemon: use sigaction() to install child_handler()\n>> - compat/mingw: allow sigaction(SIGCHLD)\n>> - compat/posix.h: track SA_RESTART fallback\n>> \n>> Futz with SIGCHLD handling in \"git daemon\".\n>> \n>> Stalled?\n>> cf. \n>> source: \n>\n> I don't think so, but definitely missing reviews (specially for patch 2)\n\nThat is what I called Stalled---stalling does not have to be due to\nauthor's inaction.\n\n> and slightly controversial.\n> ...\n> On the rationale on why this is independently useful, note that we are\n> currently relying in at least 2 \"unspecified\" behaviours:\n>\n> 1) using signal() means that it is implementation defined if SA_RESTART\n> will be enabled or not for that signal, and\n> 2) if SA_RESTART is enabled, it is implementation defined if we might get\n> interrupted in poll().\n>\n> both are resolved by using sigaction() instead, and it is up to us to\n> decide if SA_RESTART is enabled or not (which might make patch 4 obsolete\n> if we decide against).\n>\n> Carlo\n>\n> CC: Johannes Sixt on feedback for SIGCHLD in mingw which uses 17 instead\n> of 22 (cygwin and others) and therefore seem to cause signal to err\n> without setting errno as it should.\n\nThanks.\n"},{"id":"521723","messageId":"aG732RLqENitRwlv@fruit.crustytoothpaste.net","threadId":"63755","inReplyTo":"xmqqplebzgm7.fsf@gitster.g","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2025-07-09T23:14:33Z","receivedAt":"2025-07-09T23:14:35Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2025-07-08 at 00:11:12, Junio C Hamano wrote:\n> * bc/use-sha256-by-default-in-3.0 (2025-07-01) 11 commits\n> - Enable SHA-256 by default in breaking changes mode\n> - help: add a build option for default hash\n> - t5300: choose the built-in hash outside of a repo\n> - t4042: choose the built-in hash outside of a repo\n> - t1007: choose the built-in hash outside of a repo\n> - t: default to compile-time default hash if not set\n> - setup: use the default algorithm to initialize repo format\n> - Use legacy hash for legacy formats\n> - builtin: use default hash when outside a repository\n> - hash: add a constant for the legacy hash algorithm\n> - hash: add a constant for the default hash algorithm\n> \n> Prepare to flip the default hash function to SHA-256.\n> \n> Will merge to 'next'?\n> source: <20250701212237.766774-1-sandals@crustytoothpaste.net>\n\nPatrick Steinhardt thought this looked fine and I didn't have any\nintentions for another round, so I suspect it's ready.\n\nOf course, if people disagree and would like more changes, please say\nso.\n-- \nbrian m. carlson (they/them)\nToronto, Ontario, CA\n"},{"id":"521726","messageId":"xmqqecuoap89.fsf@gitster.g","threadId":"63755","inReplyTo":"aG6A19ZgxwpdJuow@nand.local","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-07-10T00:01:10Z","receivedAt":"2025-07-10T00:01:13Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Taylor Blau writes:\n\n>> * tb/midx-avoid-cruft-packs (2025-06-23) 9 commits\n>> - repack: exclude cruft pack(s) from the MIDX where possible\n>> - pack-objects: introduce '--stdin-packs=follow'\n>> - pack-objects: swap 'show_{object,commit}_pack_hint'\n>> - pack-objects: fix typo in 'show_object_pack_hint()'\n>> - pack-objects: perform name-hash traversal for unpacked objects\n>> - pack-objects: declare 'rev_info' for '--stdin-packs' earlier\n>> - pack-objects: factor out handling '--stdin-packs'\n>> - pack-objects: limit scope in 'add_object_entry_from_pack()'\n>> - pack-objects: use standard option incompatibility functions\n>>\n>> \"pack-objects\" has been taught to avoid pointing into objects in\n>> cruft packs from midx.\n>>\n>> Will merge to 'next'?\n>> source: \n>\n> I think that this one is ready to go. Since Elijah and Peff last\n> reviewed it, it hasn't changed substantially (other than a few\n> bugfix-related changes that were discovered while rolling this out at\n> GitHub).\n>\n> The series has been running on GitHub's production infrastructure for\n> the last month or two without issue, so I think this is good from a\n> stability perspective.\n>\n> I've CC'd Elijah and Peff here, since they were the last two to review\n> the series, but I don't think that they have any objections to this\n> moving along.\n\nOK. As they both seem to be active, let me wait for a bit and then\nmark it for 'next' unless we hear anything unexpected.\n\nThanks.\n"},{"id":"521727","messageId":"CABPp-BHRf52jD31ioiDj_j9eOkZk0sHxPUi1ew=m3UPd+N57OQ@mail.gmail.com","threadId":"63755","inReplyTo":"xmqqecuoap89.fsf@gitster.g","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Elijah Newren","fromEmail":"newren@gmail.com","sentAt":"2025-07-10T01:05:16Z","receivedAt":"2025-07-10T01:05:28Z","isPatch":false,"sender":{"key":"newren@gmail.com","avatar":"https://avatars.githubusercontent.com/u/5455730?v=4"},"body":"On Wed, Jul 9, 2025 at 5:01 PM Junio C Hamano wrote:\n>\n> Taylor Blau writes:\n>\n> >> * tb/midx-avoid-cruft-packs (2025-06-23) 9 commits\n> >> - repack: exclude cruft pack(s) from the MIDX where possible\n> >> - pack-objects: introduce '--stdin-packs=follow'\n> >> - pack-objects: swap 'show_{object,commit}_pack_hint'\n> >> - pack-objects: fix typo in 'show_object_pack_hint()'\n> >> - pack-objects: perform name-hash traversal for unpacked objects\n> >> - pack-objects: declare 'rev_info' for '--stdin-packs' earlier\n> >> - pack-objects: factor out handling '--stdin-packs'\n> >> - pack-objects: limit scope in 'add_object_entry_from_pack()'\n> >> - pack-objects: use standard option incompatibility functions\n> >>\n> >> \"pack-objects\" has been taught to avoid pointing into objects in\n> >> cruft packs from midx.\n> >>\n> >> Will merge to 'next'?\n> >> source: \n> >\n> > I think that this one is ready to go. Since Elijah and Peff last\n> > reviewed it, it hasn't changed substantially (other than a few\n> > bugfix-related changes that were discovered while rolling this out at\n> > GitHub).\n> >\n> > The series has been running on GitHub's production infrastructure for\n> > the last month or two without issue, so I think this is good from a\n> > stability perspective.\n> >\n> > I've CC'd Elijah and Peff here, since they were the last two to review\n> > the series, but I don't think that they have any objections to this\n> > moving along.\n>\n> OK. As they both seem to be active, let me wait for a bit and then\n> mark it for 'next' unless we hear anything unexpected.\n>\n> Thanks.\n\nYep, I think this version is good to merge to next; thanks.\n"},{"id":"521731","messageId":"xmqq8qkwad1t.fsf@gitster.g","threadId":"63755","inReplyTo":"aG732RLqENitRwlv@fruit.crustytoothpaste.net","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-07-10T04:24:14Z","receivedAt":"2025-07-10T04:24:16Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"brian m. carlson\" writes:\n\n> On 2025-07-08 at 00:11:12, Junio C Hamano wrote:\n>> * bc/use-sha256-by-default-in-3.0 (2025-07-01) 11 commits\n>> - Enable SHA-256 by default in breaking changes mode\n>> - help: add a build option for default hash\n>> - t5300: choose the built-in hash outside of a repo\n>> - t4042: choose the built-in hash outside of a repo\n>> - t1007: choose the built-in hash outside of a repo\n>> - t: default to compile-time default hash if not set\n>> - setup: use the default algorithm to initialize repo format\n>> - Use legacy hash for legacy formats\n>> - builtin: use default hash when outside a repository\n>> - hash: add a constant for the legacy hash algorithm\n>> - hash: add a constant for the default hash algorithm\n>> \n>> Prepare to flip the default hash function to SHA-256.\n>> \n>> Will merge to 'next'?\n>> source: <20250701212237.766774-1-sandals@crustytoothpaste.net>\n>\n> Patrick Steinhardt thought this looked fine and I didn't have any\n> intentions for another round, so I suspect it's ready.\n\nNo worries. During today's integration cycle, I read them over once\nagain, moved it up in the merge order in preparation for marking it\nfor 'next' [*].\n\n> Of course, if people disagree and would like more changes, please say\n> so.\n\nSurely.\n\nThanks.\n\n\n[Footnote]\n\n * The range master..seen is separated into two parts by a merge\n commit called 'jch', which is usually the version I use for my\n daily work, and I do not merge anything down to 'next' until the\n topic has spent at least half a day in 'jch'.\n"},{"id":"521732","messageId":"xmqq4ivkad17.fsf@gitster.g","threadId":"63755","inReplyTo":"CABPp-BHRf52jD31ioiDj_j9eOkZk0sHxPUi1ew=m3UPd+N57OQ@mail.gmail.com","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-07-10T04:24:36Z","receivedAt":"2025-07-10T04:24:39Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Elijah Newren writes:\n\n> On Wed, Jul 9, 2025 at 5:01 PM Junio C Hamano wrote:\n>>\n>> Taylor Blau writes:\n>>\n>> >> * tb/midx-avoid-cruft-packs (2025-06-23) 9 commits\n>> >> - repack: exclude cruft pack(s) from the MIDX where possible\n>> >> - pack-objects: introduce '--stdin-packs=follow'\n>> >> - pack-objects: swap 'show_{object,commit}_pack_hint'\n>> >> - pack-objects: fix typo in 'show_object_pack_hint()'\n>> >> - pack-objects: perform name-hash traversal for unpacked objects\n>> >> - pack-objects: declare 'rev_info' for '--stdin-packs' earlier\n>> >> - pack-objects: factor out handling '--stdin-packs'\n>> >> - pack-objects: limit scope in 'add_object_entry_from_pack()'\n>> >> - pack-objects: use standard option incompatibility functions\n>> >>\n>> >> \"pack-objects\" has been taught to avoid pointing into objects in\n>> >> cruft packs from midx.\n>> >>\n>> >> Will merge to 'next'?\n>> >> source: \n>> >\n>> > I think that this one is ready to go. Since Elijah and Peff last\n>> > reviewed it, it hasn't changed substantially (other than a few\n>> > bugfix-related changes that were discovered while rolling this out at\n>> > GitHub).\n>> >\n>> > The series has been running on GitHub's production infrastructure for\n>> > the last month or two without issue, so I think this is good from a\n>> > stability perspective.\n>> >\n>> > I've CC'd Elijah and Peff here, since they were the last two to review\n>> > the series, but I don't think that they have any objections to this\n>> > moving along.\n>>\n>> OK. As they both seem to be active, let me wait for a bit and then\n>> mark it for 'next' unless we hear anything unexpected.\n>>\n>> Thanks.\n>\n> Yep, I think this version is good to merge to next; thanks.\n\nThanks.\n"},{"id":"521733","messageId":"tuglsm3r64mkgzdh2zdrewpzydz7xmyatqxwbbzpqmltwseefc@65cbcs3pq2qg","threadId":"63755","inReplyTo":"668ce4d4-3b60-47e0-a4a5-dbf73efd1e75@kdbg.org","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Carlo Marcelo Arenas Belón","fromEmail":"carenas@gmail.com","sentAt":"2025-07-10T04:25:44Z","receivedAt":"2025-07-10T04:25:47Z","isPatch":false,"sender":{"key":"carenas@gmail.com","avatar":"https://avatars.githubusercontent.com/u/76036?v=4"},"body":"On Wed, Jul 09, 2025 at 05:04:51PM -0800, Johannes Sixt wrote:\n> Am 09.07.25 um 12:41 schrieb Carlo Marcelo Arenas Belón:\n> > CC: Johannes Sixt on feedback for SIGCHLD in mingw which uses 17 instead\n> > of 20 (cygwin and others) and therefore seem to cause signal to err\n> > without setting errno as it should.\n> \n> I don't know what the relevance of the actual number of a signal is.\n> Nobody is supposed to use the number, only the macro. But I may be\n> misjudging the situation as a bystander of this discussion.\n\nIn d28250654f (Windows: Fix signal numbers, 2009-01-22), the value for\nSIGCHLD was changed from 0 to 17 mentioning some sort of POSIX system.\n\nthe relevance comes that if I build a program in Windows that calls\n`signal(SIGCHLD)` using that number I get an error back, but nothing\non errno, but if the number would be instead 20, like in Cygwin/macOS\nsuddenly the behaviour changes and we get the expected EINVAL(20) in errno.\n\n> Furthermore, there is no such thing as \"a signal\" on Windows (outside of\n> Cygwin), let alone a SIGCHLD. Therefore, this topic about SA_RESTART is\n> irrelevant for the MinGW port.\n\nSo do you have any objection on changing the value (which should be otherwise\nunused, and irrelevanted as you pointed out) to 20 then?\n\nCarlo\n"},{"id":"521736","messageId":"51208670-eccc-493f-8a60-2bc9e3a70801@kdbg.org","threadId":"63755","inReplyTo":"tuglsm3r64mkgzdh2zdrewpzydz7xmyatqxwbbzpqmltwseefc@65cbcs3pq2qg","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Johannes Sixt","fromEmail":"j6t@kdbg.org","sentAt":"2025-07-10T07:18:04Z","receivedAt":"2025-07-10T07:18:15Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Am 10.07.25 um 06:25 schrieb Carlo Marcelo Arenas Belón:\n> In d28250654f (Windows: Fix signal numbers, 2009-01-22), the value for\n> SIGCHLD was changed from 0 to 17 mentioning some sort of POSIX system.\n> \n> the relevance comes that if I build a program in Windows that calls\n> `signal(SIGCHLD)` using that number I get an error back, but nothing\n> on errno, but if the number would be instead 20, like in Cygwin/macOS\n> suddenly the behaviour changes and we get the expected EINVAL(20) in errno.\n\n> So do you have any objection on changing the value (which should be otherwise\n> unused, and irrelevanted as you pointed out) to 20 then?\n\nI do not object to change the number. Nevertheless, I would like to\nunderstand why it makes a difference. (Currently, I am unable to look\ninto this myself, though.)\n\n-- Hannes\n\n"},{"id":"521756","messageId":"xmqqqzyo83mw.fsf@gitster.g","threadId":"63755","inReplyTo":"51208670-eccc-493f-8a60-2bc9e3a70801@kdbg.org","subject":"Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-07-10T15:30:31Z","receivedAt":"2025-07-10T15:30:34Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Sixt writes:\n\n> Am 10.07.25 um 06:25 schrieb Carlo Marcelo Arenas Belón:\n>> In d28250654f (Windows: Fix signal numbers, 2009-01-22), the value for\n>> SIGCHLD was changed from 0 to 17 mentioning some sort of POSIX system.\n>> \n>> the relevance comes that if I build a program in Windows that calls\n>> `signal(SIGCHLD)` using that number I get an error back, but nothing\n>> on errno, but if the number would be instead 20, like in Cygwin/macOS\n>> suddenly the behaviour changes and we get the expected EINVAL(20) in errno.\n>\n>> So do you have any objection on changing the value (which should be otherwise\n>> unused, and irrelevanted as you pointed out) to 20 then?\n>\n> I do not object to change the number. Nevertheless, I would like to\n> understand why it makes a difference.\n\nYeah, whoever writes the commit that changes the value needs to\nexplain why the change matters, and where the differences come from\nin the proposed log message.\n\nThanks, all.\n\n\n"}]}