{"thread":{"id":"58465","subject":"What's cooking in git.git (Sep 2022, #05; Mon, 19)","startedAt":"2022-09-20T04:21:19Z","lastAt":"2022-09-20T04:21:19Z","messageCount":1,"participants":["Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"463271","messageId":"xmqq5yhi8ymi.fsf@gitster.g","threadId":"58465","inReplyTo":null,"subject":"What's cooking in git.git (Sep 2022, #05; Mon, 19)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-09-20T04:21:09Z","receivedAt":"2022-09-20T04:21:19Z","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 future\nrelease). Commits prefixed with '-' are only in 'seen', and aren't\nconsidered \"accepted\" at all. A topic without enough support may be\ndiscarded after a long period of no activity.\n\nA few more topics have been merged to the 'master' branch. We plan\nto tag -rc1 in a few days (but expect no movement on 'master' or\n'next' tomorrow). There are a few topics that are marked with the\n\"Merge to 'next'?\" marker, which can use your help ;-) After -rc1\ngets tagged, the 'master' branch will go in the \"regression fixes\nonly\" mode (cf. https://tinyurl.com/gitCal).\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-vcs/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* ad/t1800-cygwin (2022-09-15) 1 commit\n (merged to 'next' on 2022-09-15 at 9667abb48c)\n + t1800: correct test to handle Cygwin\n\n Test fix.\n source: <20220915075717.425673-1-adam@dinwoodie.org>\n\n\n* es/chainlint (2022-09-12) 19 commits\n (merged to 'next' on 2022-09-12 at 577e59143f)\n + chainlint: colorize problem annotations and test delimiters\n (merged to 'next' on 2022-09-08 at eab3357b05)\n + t: retire unused chainlint.sed\n + t/Makefile: teach `make test` and `make prove` to run chainlint.pl\n + test-lib: replace chainlint.sed with chainlint.pl\n + test-lib: retire \"lint harder\" optimization hack\n + t/chainlint: add more chainlint.pl self-tests\n + chainlint.pl: allow `|| echo` to signal failure upstream of a pipe\n + chainlint.pl: complain about loops lacking explicit failure handling\n + chainlint.pl: don't flag broken &&-chain if failure indicated explicitly\n + chainlint.pl: don't flag broken &&-chain if `$?` handled explicitly\n + chainlint.pl: don't require `&` background command to end with `&&`\n + t/Makefile: apply chainlint.pl to existing self-tests\n + chainlint.pl: don't require `return|exit|continue` to end with `&&`\n + chainlint.pl: validate test scripts in parallel\n + chainlint.pl: add parser to identify test definitions\n + chainlint.pl: add parser to validate tests\n + chainlint.pl: add POSIX shell parser\n + chainlint.pl: add POSIX shell lexical analyzer\n + t: add skeleton chainlint.pl\n\n Revamp chainlint script for our tests.\n source: \n source: \n\n\n* jk/list-objects-filter-cleanup (2022-09-12) 5 commits\n (merged to 'next' on 2022-09-12 at 33cb79c924)\n + list-objects-filter: convert filter_spec to a strbuf\n + list-objects-filter: add and use initializers\n + list-objects-filter: handle null default filter spec\n + list-objects-filter: don't memset after releasing filter struct\n + Merge branch 'jk/plug-list-object-filter-leaks' into jk/list-objects-filter-cleanup\n\n A couple of bugfixes with code clean-up.\n source: \n\n\n* sy/mv-out-of-cone (2022-09-09) 10 commits\n (merged to 'next' on 2022-09-12 at 7cb7b41779)\n + builtin/mv.c: fix possible segfault in add_slash()\n (merged to 'next' on 2022-08-17 at 2316d9ce4d)\n + mv: check overwrite for in-to-out move\n + advice.h: add advise_on_moving_dirty_path()\n + mv: cleanup empty WORKING_DIRECTORY\n + mv: from in-cone to out-of-cone\n + mv: remove BOTH from enum update_mode\n + mv: check if is a SKIP_WORKTREE_DIR\n + mv: free the with_slash in check_dir_in_index()\n + mv: rename check_dir_in_index() to empty_dir_has_sparse_contents()\n + t7002: add tests for moving from in-cone to out-of-cone\n\n \"git mv A B\" in a sparsely populated working tree can be asked to\n move a path from a directory that is \"in cone\" to another directory\n that is \"out of cone\". Handling of such a case has been improved.\n source: <20220809120910.2021413-1-shaoxuan.yuan02@gmail.com>\n source: <20220909222736.279362-1-shaoxuan.yuan02@gmail.com>\n\n\n* vd/scalar-to-main (2022-09-02) 9 commits\n (merged to 'next' on 2022-09-14 at 230bf89c01)\n + Documentation/technical: include Scalar technical doc\n + t/perf: add 'GIT_PERF_USE_SCALAR' run option\n + t/perf: add Scalar performance tests\n + scalar-clone: add test coverage\n + scalar: add to 'git help -a' command list\n + scalar: implement the `help` subcommand\n + git help: special-case `scalar`\n + scalar: include in standard Git build & installation\n + scalar: fix command documentation section header\n\n Hoist the remainder of \"scalar\" out of contrib/ to the main part of\n the codebase.\n source: \n\n\n* zh/ls-files-format (2022-09-12) 1 commit\n (merged to 'next' on 2022-09-12 at 91dda58387)\n + ls-files: fix black space in error message\n\n Typofix in the UI of a topic that has graduated to 'master'.\n source: \n\n--------------------------------------------------\n[New Topics]\n\n* fz/help-doublofix (2022-09-16) 1 commit\n (merged to 'next' on 2022-09-19 at 3ec5906f4e)\n + help: fix doubled words in explanation for developer interfaces\n\n Typofix for topic already in -rc0.\n\n Will merge to 'master'.\n source: \n\n\n* so/diff-merges-cleanup (2022-09-16) 3 commits\n - diff-merges: clarify log.diffMerges documentation\n - diff-merges: cleanup set_diff_merges()\n - diff-merges: cleanup func_by_opt()\n\n Code clean-up.\n\n Will merge to 'next'?\n source: <20220914193102.5275-1-sorganov@gmail.com>\n\n\n* tz/tech-docs-to-help-fix (2022-09-16) 2 commits\n (merged to 'next' on 2022-09-19 at 4a13143da1)\n + api docs: link to html version of api-trace2\n + docs: fix a few recently broken links\n\n Docfix for topic already in -rc0.\n\n Will merge to 'master'.\n source: <20220916062303.3736166-2-tmz@pobox.com>\n\n\n* ja/rebase-i-avoid-amending-self (2022-09-19) 1 commit\n - sequencer: avoid dropping fixup commit that targets self via commit-ish\n\n \"git rebase -i\" can mistakenly attempt to apply a fixup to a commit\n itself, which has been corrected.\n\n Will merge to 'next'?\n source: <20220918121053.880225-1-aclopte@gmail.com>\n\n\n* ml/commit-graph-expire-dir-leak-fix (2022-09-19) 1 commit\n (merged to 'next' on 2022-09-19 at e3211e888e)\n + commit-graph: Fix missing closedir in expire_commit_graphs\n\n A result from opendir() was leaking in the commit-graph expiration\n codepath, which has been plugged.\n\n Will merge to 'master'.\n source: <20220919141441.5644-1-linmq006@gmail.com>\n\n\n* vd/scalar-generalize-diagnose (2022-09-19) 1 commit\n (merged to 'next' on 2022-09-19 at e03e8a6e4a)\n + diagnose.c: refactor to safely use 'd_type'\n\n Portability fix.\n\n Will merge to 'master'.\n source: \n\n\n* ac/fuzzers (2022-09-19) 1 commit\n - fuzz: reorganise the path for existing oss-fuzz fuzzers\n\n source: \n\n\n* hn/parse-worktree-ref (2022-09-19) 1 commit\n - refs: unify parse_worktree_ref() and ref_type()\n\n source: \n\n--------------------------------------------------\n[Stalled]\n\n* es/mark-gc-cruft-as-experimental (2022-08-03) 2 commits\n - config: let feature.experimental imply gc.cruftPacks=true\n - gc: add tests for --cruft and friends\n\n Enable gc.cruftpacks by default for those who opt into\n feature.experimental setting.\n\n Expecting a reroll.\n cf. <220804.86a68ke9d5.gmgdl@evledraar.gmail.com>\n cf. <6803b725-526e-a1c8-f15c-a9ed4a144d4c@github.com>\n source: <20220803205721.3686361-1-emilyshaffer@google.com>\n\n\n* es/doc-creation-factor-fix (2022-07-28) 2 commits\n - range-diff: clarify --creation-factor=\n - format-patch: clarify --creation-factor=\n\n Expecting a reroll by somebody more familiar with the logic\n cf. \n source: <7229p500-p2r4-on87-6802-8o90s36rr3s4@tzk.qr>\n\n\n* cw/remote-object-info (2022-08-13) 7 commits\n - SQUASH???\n - cat-file: add remote-object-info to batch-command\n - transport: add client support for object-info\n - serve: advertise object-info feature\n - protocol-caps: initialization bug fix\n - fetch-pack: move fetch initialization\n - fetch-pack: refactor packet writing\n\n A client component to talk with the object-info endpoint.\n\n Expecting a reroll.\n cf. <20220728230210.2952731-1-calvinwan@google.com>\n cf. \n source: <20220728230210.2952731-1-calvinwan@google.com>\n\n--------------------------------------------------\n[Cooking]\n\n* ed/fsmonitor-on-networked-macos (2022-09-19) 5 commits\n - fsmonitor: add documentation for allowRemote and socketDir options\n - fsmonitor: deal with synthetic firmlinks on macOS\n - fsmonitor: avoid socket location check if using hook\n - fsmonitor: relocate socket file if .git directory is remote\n - fsmonitor: refactor filesystem checks to common interface\n\n By default, use of fsmonitor on a repository on networked\n filesystem is disabled. Add knobs to make it workable on macOS.\n\n Will merge to 'next'?\n source: \n\n\n* rj/branch-edit-description-with-nth-checkout (2022-09-12) 2 commits\n - branch: support for shortcuts like @{-1} completed\n - branch: refactor \"edit_description\" code path\n\n \"git branch --edit-description @{-1}\" is now a way to edit branch\n description of the branch you were on before switching to the\n current branch.\n\n Needs review.\n source: <7abdb5a9-5707-7897-4196-8d2892beeb81@gmail.com>\n\n\n* mj/credential-helper-auth-headers (2022-09-13) 8 commits\n - http: set specific auth scheme depending on credential\n - http: move proactive auth to first slot creation\n - http: store all request headers on active_request_slot\n - credential: add WWW-Authenticate header to cred requests\n - http: read HTTP WWW-Authenticate response headers\n - osxkeychain: clarify that we ignore unknown lines\n - netrc: ignore unknown lines (do not die)\n - wincred: ignore unknown lines (do not die)\n\n RFC\n source: \n\n\n* ec/reftable-pass-pq-entry-by-reference (2022-09-15) 1 commit\n (merged to 'next' on 2022-09-15 at 928e75c7d1)\n + reftable: use a pointer for pq_entry param\n\n Small code clean-up in reftable implementation.\n\n Will merge to 'master'.\n source: <1833f3928cb.acf3c97d869879.7909589521159235166@elijahpepe.com>\n\n\n* jc/environ-docs (2022-09-16) 5 commits\n - environ: GIT_INDEX_VERSION affects not just a new repository\n - environ: simplify description of GIT_INDEX_FILE\n - environ: GIT_FLUSH should be made a usual Boolean\n - environ: explain Boolean environment variables\n - environ: document GIT_SSL_NO_VERIFY\n\n Documentation on various Boolean GIT_* environment variables have\n been clarified.\n\n Will merge to 'next'?\n source: <20220915160659.126441-1-gitster@pobox.com>\n\n\n* rs/diff-caret-bang-with-parents (2022-09-15) 6 commits\n - revision: add parents after child for ^!\n - revision: rename add_parents_only() to add_nth_parent()\n - revision: factor out add_parents()\n - revision: factor out add_parent()\n - revision: factor out get_commit()\n - revision: use strtol_i() for exclude_parent\n\n \"git diff rev^!\" did not show combined diff to go to the rev from\n its parents.\n\n Needs review.\n source: \n\n\n* ab/doc-synopsis-and-cmd-usage (2022-09-07) 34 commits\n - tests: start asserting that *.txt SYNOPSIS matches -h output\n - doc txt & -h consistency: make \"worktree\" consistent\n - worktree: define subcommand -h in terms of command -h\n - reflog doc: list real subcommands up-front\n - doc txt & -h consistency: make \"commit\" consistent\n - doc txt & -h consistency: make \"diff-tree\" consistent\n - doc txt & -h consistency: use \"[