{"thread":{"id":"57273","subject":"What's cooking in git.git (Jan 2022, #05; Wed, 19)","startedAt":"2022-01-20T02:12:49Z","lastAt":"2022-01-20T15:15:08Z","messageCount":5,"participants":["Junio C Hamano","Han-Wen Nienhuys"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"446530","messageId":"xmqqwnivjgtg.fsf@gitster.g","threadId":"57273","inReplyTo":null,"subject":"What's cooking in git.git (Jan 2022, #05; Wed, 19)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-01-20T02:12:43Z","receivedAt":"2022-01-20T02:12:49Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"We are at -rc2 now. A few more topics are now in 'next' but it is\nnot a big deal anyway, as they are not about any regression fixes\nand will not go anywhere during the prerelease freeze.\n\nHere 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',\nwhich means nothing more than that I have found them of interest for\nsome reason (like \"it may have hard-to-resolve conflicts with\nanother topic already in flight\" or \"this may turn out to be\nuseful\"). Do not read too much into a topic being in (or not in)\n'seen'. The ones marked with '.' do not appear in any of the\nintegration branches, but I am still holding onto them.\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* da/rhel7-lacks-uncompress2-and-c99 (2022-01-16) 1 commit\n (merged to 'next' on 2022-01-16 at 1aeeab2aa6)\n + build: centos/RHEL 7 ships with an older gcc and zlib\n\n Adjust build on RHEL 7 to explicitly ask C99 support and use\n the fallback implementation of uncompress2 we ship.\n source: <20220116020520.26895-1-davvid@gmail.com>\n\n\n* jc/freebsd-without-c99-only-build (2022-01-18) 1 commit\n (merged to 'next' on 2022-01-18 at 6ab02e9ee4)\n + Makefile: FreeBSD cannot do C99-or-below build\n\n FreeBSD 13.0 headers have unconditional dependency on C11 language\n features, and adding -std=gnu99 to DEVELOPER_CFLAGS would just\n break the developer build.\n source: \n\n\n* js/branch-track-inherit (2022-01-18) 1 commit\n (merged to 'next' on 2022-01-18 at 6a6a1b2bbf)\n + branch,checkout: fix --track usage strings\n\n \"git branch -h\" incorrectly said \"--track[=direct|inherit]\",\n implying that \"--trackinherit\" is a valid option, which has been\n corrected.\n source: <3de40324bea6a1dd9bca2654721471e3809e87d8.1642538935.git.steadmon@google.com>\n\n--------------------------------------------------\n[New Topics]\n\n* en/merge-ort-restart-optim-fix (2022-01-17) 1 commit\n (merged to 'next' on 2022-01-19 at 84da10b057)\n + merge-ort: avoid assuming all renames detected\n\n The merge-ort misbehaved when merge.renameLimit configuration is\n set too low and failed to find all renames.\n\n Will cook in 'next'.\n source: \n\n\n* jh/p4-various-fixups (2022-01-16) 23 commits\n . git-p4: seperate multiple statements onto seperate lines\n . git-p4: move inline comments to line above\n . git-p4: only seperate code blocks by a single empty line\n . git-p4: compare to singletons with \"is\" and \"is not\"\n . git-p4: normalize indentation of lines in conditionals\n . git-p4: ensure there is a single space around all operators\n . git-p4: ensure every comment has a single #\n . git-p4: remove spaces between dictionary keys and colons\n . git-p4: remove redundant backslash-continuations inside brackets\n . git-p4: remove extraneous spaces before function arguments\n . git-p4: place a single space after every comma\n . git-p4: removed brackets when assigning multiple return values\n . git-p4: remove spaces around default arguments\n . git-p4: remove padding from lists, tuples and function arguments\n . git-p4: sort and de-duplcate pylint disable list\n . git-p4: remove commented code\n . git-p4: convert descriptive class and function comments into docstrings\n . git-p4: improve consistency of docstring formatting\n . git-p4: indent with 4-spaces\n . git-p4: remove unneeded semicolons from statements\n . git-p4: add blank lines between functions and class definitions\n . Merge branch 'jh/p4-spawning-external-commands-cleanup' into jh/p4-various-fixups\n . Merge branch 'jh/p4-fix-use-of-process-error-exception' into jh/p4-various-fixups\n (this branch uses jh/p4-fix-use-of-process-error-exception and jh/p4-spawning-external-commands-cleanup.)\n\n Various cleanups to \"git p4\".\n\n Breaks its own test suite.\n source: <20220116160550.514637-1-jholdsworth@nvidia.com>\n\n\n* po/readme-mention-contributor-hints (2022-01-17) 1 commit\n (merged to 'next' on 2022-01-19 at 7e14690eb9)\n + README.md: add CodingGuidelines and a link for Translators\n\n Doc update.\n\n Will cook in 'next'.\n source: \n\n\n* tl/doc-cli-options-first (2022-01-17) 1 commit\n (merged to 'next' on 2022-01-19 at 9ec14cfe73)\n + git-cli.txt: clarify \"options first and then args\"\n\n We explain that revs come first before the pathspec among command\n line arguments, but did not spell out that dashed options come\n before other args, which has been corrected.\n\n Will cook in 'next'.\n source: \n\n\n* rs/bisect-executable-not-found (2022-01-19) 4 commits\n - bisect--helper: double-check run command on exit code 126 and 127\n - bisect: document run behavior with exit codes 126 and 127\n - bisect--helper: release strbuf and strvec on run error\n - bisect--helper: report actual bisect_state() argument on error\n\n source: \n\n--------------------------------------------------\n[Stalled]\n\n* je/http-better-error-output (2021-12-03) 1 commit\n . http-backend: give a hint that web browser access is not supported\n\n When the http-backend program, which is the server-side component\n for the smart HTTP transport, sends a \"404 Not found\" error, we\n deliberately did not say anything to the requesting client. We now\n send a message back to the browser to tell the user that they do\n not want to visit the URL via their browser, instead of a totally\n blank page.\n\n Expecting a reroll.\n Breaks its self tests.\n cf. <7r23s082-o3q0-479o-srqn-r45q778s5nq7@vanv.qr>\n source: <20211202102855.23907-1-jengelh@inai.de>\n\n\n* cb/save-term-across-editor-invocation (2021-12-01) 3 commits\n - fixup! editor: allow for saving/restoring terminal state\n - editor: allow for saving/restoring terminal state\n - terminal: teach save_term to fail when not foreground\n\n Some editors are reported to leave the terminal in funny state\n after they exit on Windows. Work it around by saving and restoring\n the terminal state when needed.\n\n Expecting a reroll.\n cf. \n source: <20211202035446.1154-1-carenas@gmail.com>\n\n\n* ar/submodule-update (2021-10-13) 9 commits\n . submodule--helper: rename helper functions\n . submodule--helper: remove unused helpers\n . submodule: move core cmd_update() logic to C\n . submodule--helper: run update using child process struct\n . submodule--helper: allow setting superprefix for init_submodule()\n . submodule--helper: refactor get_submodule_displaypath()\n . submodule--helper: rename helpers for update-clone\n . submodule--helper: get remote names from any repository\n . submodule--helper: split up ensure_core_worktree()\n\n Rewrite of \"git submodule update\" in C.\n\n Expecting a reroll?\n cf. \n source: <20211013051805.45662-10-raykar.ath@gmail.com>\n\n--------------------------------------------------\n[Cooking]\n\n* ds/sparse-checkout-requires-per-worktree-config (2022-01-14) 6 commits\n . worktree: copy sparse-checkout patterns and config on add\n . sparse-checkout: use repo_config_set_worktree_gently()\n . config: add repo_config_set_worktree_gently()\n . worktree: add 'init-worktree-config' subcommand\n . config: make some helpers repo-aware\n . setup: use a repository when upgrading format\n\n \"git sparse-checkout\" wants to work with per-worktree configration,\n but did not work well in a worktree attached to a bare repository.\n\n Expecting an update.\n cf. <1db0f601-4769-15c0-cd58-ecddfa1fc9d5@gmail.com>\n Introduces new leaks.\n cf. https://github.com/git/git/runs/4823667255?check_suite_focus=true\n source: \n\n\n* pw/add-p-hunk-split-fix (2022-01-12) 2 commits\n (merged to 'next' on 2022-01-19 at ea57b2c9a6)\n + builtin add -p: fix hunk splitting\n + t3701: clean up hunk splitting tests\n\n \"git add -p\" rewritten in C regressed hunk splitting in some cases,\n which has been corrected.\n\n Will cook in 'next'.\n source: \n\n\n* gc/fetch-negotiate-only-early-return (2022-01-18) 3 commits\n (merged to 'next' on 2022-01-19 at 0f15147cfa)\n + fetch --negotiate-only: do not update submodules\n + fetch: skip tasks related to fetching objects\n + fetch: use goto cleanup in cmd_fetch()\n\n \"git fetch --negotiate-only\" is an internal command used by \"git\n push\" to figure out which part of our history is missing from the\n other side. It should never recurse into submodules even when\n fetch.recursesubmodules configuration variable is set, nor it\n should trigger \"gc\". The code has been tightened up to ensure it\n only does common ancestry discovery and nothing else.\n\n Will cook in 'next'.\n source: <20220119000056.58503-1-chooglen@google.com>\n\n\n* jh/p4-fix-use-of-process-error-exception (2022-01-06) 1 commit\n (merged to 'next' on 2022-01-10 at 49d529bfd7)\n + git-p4: fix instantiation of CalledProcessError\n (this branch is used by jh/p4-various-fixups.)\n\n Will cook in 'next'.\n source: <20220106214156.90967-1-jholdsworth@nvidia.com>\n\n\n* jh/p4-spawning-external-commands-cleanup (2022-01-06) 3 commits\n (merged to 'next' on 2022-01-10 at 54b36b4e66)\n + git-p4: don't print shell commands as python lists\n + git-p4: pass command arguments as lists instead of using shell\n + git-p4: don't select shell mode using the type of the command argument\n (this branch is used by jh/p4-various-fixups.)\n\n Will cook in 'next'.\n source: <20220106214035.90725-1-jholdsworth@nvidia.com>\n\n\n* pb/pull-rebase-autostash-fix (2022-01-14) 1 commit\n (merged to 'next' on 2022-01-14 at 83a388a7e2)\n + pull --rebase: honor rebase.autostash when fast-forwarding\n\n \"git pull --rebase\" ignored the rebase.autostash configuration\n variable when the remote history is a descendant of our history,\n which has been corrected.\n\n Will cook in 'next'.\n source: \n\n\n* rs/grep-expr-cleanup (2022-01-06) 4 commits\n (merged to 'next' on 2022-01-10 at b70a3bb0fa)\n + grep: use grep_and_expr() in compile_pattern_and()\n + grep: extract grep_binexp() from grep_or_expr()\n + grep: use grep_not_expr() in compile_pattern_not()\n + grep: use grep_or_expr() in compile_pattern_or()\n\n Code clean-up.\n\n Will cook in 'next'.\n source: \n\n\n* fs/ssh-signing-crlf (2022-01-07) 1 commit\n (merged to 'next' on 2022-01-19 at 76b86faafb)\n + gpg-interface: trim CR from ssh-keygen\n\n The code path that verifies signatures made with ssh were made to\n work better on a system with CRLF line endings.\n\n Will cook in 'next'.\n source: <20220107090735.580225-1-fs@gigacodes.de>\n\n\n* jc/qsort-s-alignment-fix (2022-01-07) 2 commits\n (merged to 'next' on 2022-01-10 at 329fd6e09a)\n + stable-qsort: avoid using potentially unaligned access\n + compat/qsort_s.c: avoid using potentially unaligned access\n\n Fix a hand-rolled alloca() imitation that may have violated\n alignment requirement of data being sorted in compatibility\n implementation of qsort_s() and stable qsort().\n\n Will cook in 'next'.\n source: \n source: \n\n\n* ps/avoid-unnecessary-hook-invocation-with-packed-refs (2022-01-17) 6 commits\n - refs: skip hooks when deleting uncovered packed refs\n - refs: do not execute reference-transaction hook on packing refs\n - refs: demonstrate excessive execution of the reference-transaction hook\n - refs: allow skipping the reference-transaction hook\n - refs: allow passing flags when beginning transactions\n - refs: extract packed_refs_delete_refs() to allow control of transaction\n\n Because a deletion of ref would need to remove it from both the\n loose ref store and the packed ref store, a delete-ref operation\n that logically removes one ref may end up invoking ref-transaction\n hook twice, which has been corrected.\n\n Introduces new leaks when merged to 'seen'.\n source: \n\n\n* rs/apply-symlinks-use-strset (2022-01-07) 1 commit\n (merged to 'next' on 2022-01-10 at 32497a67d5)\n + apply: use strsets to track symlinks\n\n \"git apply\" (ab)used the util pointer of the string-list to keep\n track of how each symbolic link needs to be handled, which has been\n simplified by using strset.\n\n Will cook in 'next'.\n source: <8739caad-aa3d-1f0f-b5dd-6174a8e059f6@web.de>\n\n\n* ld/sparse-index-bash-completion (2022-01-10) 3 commits\n - sparse-checkout: limit tab completion to a single level\n - sparse-checkout: custom tab completion\n - sparse-checkout: custom tab completion tests\n\n The command line completion (in contrib/) learns to complete\n arguments give to \"git sparse-checkout\" command.\n source: \n\n\n* bc/clarify-eol-attr (2022-01-12) 2 commits\n - docs: correct documentation about eol attribute\n - t0027: add tests for eol without text in .gitattributes\n\n Doc and test update around the eol attribute.\n source: <20220111021507.531736-1-sandals@crustytoothpaste.net>\n\n\n* jz/rev-list-exclude-first-parent-only (2022-01-12) 1 commit\n - git-rev-list: add --exclude-first-parent-only flag\n\n \"git log\" and friends learned an option --exclude-first-parent-only\n to propagate UNINTERESTING bit down only along the first-parent\n chain, just like --first-parent option shows commits that lack the\n UNINTERESTING bit only along the first-parent chain.\n source: <20220111213941.30129-1-jerry@skydio.com>\n\n\n* en/present-despite-skipped (2022-01-14) 6 commits\n - Accelerate clear_skip_worktree_from_present_files() by caching\n - Update documentation related to sparsity and the skip-worktree bit\n - repo_read_index: clear SKIP_WORKTREE bit from files present in worktree\n - unpack-trees: fix accidental loss of user changes\n - t1011: add testcase demonstrating accidental loss of user modifications\n - Merge branch 'vd/sparse-clean-etc' into en/present-despite-skipped\n (this branch uses vd/sparse-clean-etc.)\n\n In sparse-checkouts, files mis-marked as missing from the working tree\n could lead to later problems. Such files were hard to discover, and\n harder to correct. Automatically detecting and correcting the marking\n of such files has been added to avoid these problems.\n source: \n\n\n* bc/csprng-mktemps (2022-01-17) 2 commits\n - wrapper: use a CSPRNG to generate random file names\n - wrapper: add a helper to generate numbers from a CSPRNG\n\n Pick a better random number generator and use it when we prepare\n temporary filenames.\n\n Are we solving the right problem?\n cf. <220118.86zgntpegy.gmgdl@evledraar.gmail.com>\n source: <20220117215617.843190-1-sandals@crustytoothpaste.net>\n\n\n* jc/reflog-parse-options (2022-01-10) 2 commits\n (merged to 'next' on 2022-01-12 at 1659e49c4b)\n + builtin/reflog.c: use parse-options api for expire, delete subcommands\n + Merge branch 'ab/reflog-prep' into jc/reflog-parse-options\n\n Use the parse-options API in \"git reflog\" command.\n\n Will cook in 'next'.\n source: \n\n\n* vd/sparse-clean-etc (2022-01-13) 9 commits\n - update-index: reduce scope of index expansion in do_reupdate\n - update-index: integrate with sparse index\n - update-index: add tests for sparse-checkout compatibility\n - checkout-index: integrate with sparse index\n - checkout-index: add --ignore-skip-worktree-bits option\n - checkout-index: expand sparse checkout compatibility tests\n - clean: integrate with sparse index\n - reset: reorder wildcard pathspec conditions\n - reset: fix validation in sparse index test\n (this branch is used by en/present-despite-skipped.)\n\n \"git update-index\", \"git checkout-index\", and \"git clean\" are\n taught to work better with the sparse checkout feature.\n source: \n\n\n* ms/update-index-racy (2022-01-07) 4 commits\n (merged to 'next' on 2022-01-14 at 705a33f63b)\n + update-index: refresh should rewrite index in case of racy timestamps\n + t7508: add tests capturing racy timestamp handling\n + t7508: fix bogus mtime verification\n + test-lib: introduce API for verifying file mtime\n\n \"git update-index --refresh\" has been taught to deal better with\n racy timestamps (just like \"git status\" already does).\n\n Will cook in 'next'.\n source: \n\n\n* jc/find-header (2022-01-06) 1 commit\n (merged to 'next' on 2022-01-10 at 8a13b4f0b3)\n + receive-pack.c: consolidate find header logic\n\n Code clean-up.\n\n Will cook in 'next'.\n source: \n\n\n* jc/name-rev-stdin (2022-01-10) 2 commits\n (merged to 'next' on 2022-01-19 at a58e05fabe)\n + name-rev.c: use strbuf_getline instead of limited size buffer\n + name-rev: deprecate --stdin in favor of --annotate-stdin\n\n \"git name-rev --stdin\" does not behave like usual \"--stdin\" at\n all. Start the process of renaming it to \"--annotate-stdin\".\n\n Will cook in 'next'.\n source: \n\n\n* en/remerge-diff (2021-12-30) 10 commits\n - merge-ort: mark conflict/warning messages from inner merges as omittable\n - show, log: include conflict/warning messages in --remerge-diff headers\n - diff: add ability to insert additional headers for paths\n - merge-ort: format messages slightly different for use in headers\n - merge-ort: mark a few more conflict messages as omittable\n - merge-ort: capture and print ll-merge warnings in our preferred fashion\n - ll-merge: make callers responsible for showing warnings\n - log: clean unneeded objects during `log --remerge-diff`\n - show, log: provide a --remerge-diff capability\n - Merge branch 'ns/tmp-objdir' into en/remerge-diff\n\n \"git log --remerge-diff\" shows the difference from mechanical merge\n result and the merge result that is actually recorded.\n\n Plug new leaks?\n cf. <220119.86pmonn2mb.gmgdl@evledraar.gmail.com>\n source: \n\n\n* bs/forbid-i18n-of-protocol-token-in-fetch-pack (2021-12-22) 2 commits\n - fixup! fetch-pack: parameterize message containing 'ready' keyword\n - fetch-pack: parameterize message containing 'ready' keyword\n\n L10n support for a few error messages.\n\n Expecting an ack for fixup.\n source: <20211222075805.19027-1-bagasdotme@gmail.com>\n\n\n* gc/branch-recurse-submodules (2022-01-10) 6 commits\n - branch: add --recurse-submodules option for branch creation\n - builtin/branch: clean up action-picking logic in cmd_branch()\n - branch: add a dry_run parameter to create_branch()\n - branch: make create_branch() always create a branch\n - branch: move --set-upstream-to behavior to dwim_and_setup_tracking()\n - Merge branch 'js/branch-track-inherit' into gc/branch-recurse-submodules\n\n \"git branch\" learned the \"--recurse-submodules\" option.\n\n Expecting a reroll.\n cf. \n source: <20211220233459.45739-1-chooglen@google.com>\n\n\n* hn/reftable-coverity-fixes (2021-12-22) 18 commits\n - reftable: be more paranoid about 0-length memcpy calls\n - reftable: add print functions to the record types\n - reftable: make reftable_record a tagged union\n - reftable: remove outdated file reftable.c\n - reftable: implement record equality generically\n - reftable: make reftable-record.h function signatures const correct\n - reftable: handle null refnames in reftable_ref_record_equal\n - reftable: drop stray printf in readwrite_test\n - reftable: order unittests by complexity\n - reftable: all xxx_free() functions accept NULL arguments\n - reftable: fix resource warning\n - reftable: ignore remove() return value in stack_test.c\n - reftable: check reftable_stack_auto_compact() return value\n - reftable: fix resource leak blocksource.c\n - reftable: fix resource leak in block.c error path\n - reftable: fix OOB stack write in print functions\n - Merge branch 'hn/create-reflog-simplify' into hn/reftable-coverity-fixes\n - Merge branch 'hn/reftable' into hn/reftable-coverity-fixes\n\n Problems identified by Coverity in the reftable code have been\n corrected.\n\n Expecting a reroll.\n cf. <211228.86lf04j0lg.gmgdl@evledraar.gmail.com>\n source: \n\n\n* tb/midx-bitmap-corruption-fix (2022-01-04) 9 commits\n - pack-bitmap.c: gracefully fallback after opening pack/MIDX\n - midx: read `RIDX` chunk when present\n - t/lib-bitmap.sh: parameterize tests over reverse index source\n - t5326: move tests to t/lib-bitmap.sh\n - t5326: extract `test_rev_exists`\n - t5326: drop unnecessary setup\n - pack-revindex.c: instrument loading on-disk reverse index\n - midx.c: make changing the preferred pack safe\n - t5326: demonstrate bitmap corruption after permutation\n\n A bug that made multi-pack bitmap and the object order out-of-sync\n (hence the .midx data gets corrupted) has been fixed.\n\n Waiting for a hopefully final review.\n cf. \n source: \n\n\n* pw/fix-some-issues-in-reset-head (2021-12-08) 14 commits\n - rebase -m: don't fork git checkout\n - rebase --apply: set ORIG_HEAD correctly\n - rebase --apply: fix reflog\n - reset_head(): take struct rebase_head_opts\n - rebase: cleanup reset_head() calls\n - reset_head(): make default_reflog_action optional\n - reset_head(): factor out ref updates\n - create_autostash(): remove unneeded parameter\n - reset_head(): remove action parameter\n - rebase --apply: don't run post-checkout hook if there is an error\n - rebase: do not remove untracked files on checkout\n - rebase: pass correct arguments to post-checkout hook\n - t5403: refactor rebase post-checkout hook tests\n - rebase: factor out checkout for up to date branch\n\n Fix \"some issues\" in a helper function reset_head().\n\n Expecting a reroll.\n cf. \n cf. \n cf. \n cf. \n cf. \n source: \n\n\n* ab/cat-file (2022-01-12) 12 commits\n (merged to 'next' on 2022-01-12 at ee4d43041d)\n + cat-file: s/_/-/ in typo'd usage_msg_optf() message\n + cat-file: don't whitespace-pad \"(...)\" in SYNOPSIS and usage output\n (merged to 'next' on 2022-01-05 at e145efa605)\n + cat-file: use GET_OID_ONLY_TO_DIE in --(textconv|filters)\n + object-name.c: don't have GET_OID_ONLY_TO_DIE imply *_QUIETLY\n + cat-file: correct and improve usage information\n + cat-file: fix remaining usage bugs\n + cat-file: make --batch-all-objects a CMDMODE\n + cat-file: move \"usage\" variable to cmd_cat_file()\n + cat-file docs: fix SYNOPSIS and \"-h\" output\n + parse-options API: add a usage_msg_optf()\n + cat-file tests: test messaging on bad objects/paths\n + cat-file tests: test bad usage\n\n Assorted updates to \"git cat-file\", especially \"-h\".\n\n Will cook in 'next'.\n source: \n source: \n\n\n* ab/grep-patterntype (2022-01-18) 10 commits\n - grep.[ch]: remove GREP_PATTERN_TYPE_UNSPECIFIED\n - grep: simplify config parsing and option parsing\n - grep.c: do \"if (bool && memchr())\" not \"if (memchr() && bool)\"\n - grep.h: make \"grep_opt.pattern_type_option\" use its enum\n - grep API: call grep_config() after grep_init()\n - grep.c: don't pass along NULL callback value\n - built-ins: trust the \"prefix\" from run_builtin()\n - grep tests: add missing \"grep.patternType\" config tests\n - log tests: check if grep_config() is called by \"log\"-like cmds\n - grep.h: remove unused \"regex_t regexp\" from grep_opt\n\n Some code clean-up in the \"git grep\" machinery.\n\n Looking good, except for the last two steps.\n source: \n\n\n* js/use-builtin-add-i (2021-12-01) 2 commits\n - add -i: default to the built-in implementation\n - t2016: require the PERL prereq only when necessary\n\n \"git add -i\" was rewritten in C some time ago and has been in\n testing; the reimplementation is now exposed to general public by\n default.\n\n On hold.\n There are known breakages on macOS.\n cf. \n source: \n\n\n* jt/conditional-config-on-remote-url (2022-01-18) 2 commits\n (merged to 'next' on 2022-01-19 at 3c2df266eb)\n + config: include file if remote URL matches a glob\n + config: make git_config_include() static\n\n The conditional inclusion mechanism of configuration files using\n \"[includeIf ]\" learns to base its decision on the\n URL of the remote repository the repository interacts with.\n\n Will cook in 'next'.\n source: \n\n\n* ab/ambiguous-object-name (2022-01-13) 6 commits\n - object-name: re-use \"struct strbuf\" in show_ambiguous_object()\n - object-name: iterate ambiguous objects before showing header\n - object-name: show date for ambiguous tag objects\n - object-name: make ambiguous object output translatable\n - object-name: explicitly handle OBJ_BAD in show_ambiguous_object()\n - object-name tests: add tests for ambiguous object blind spots\n\n Error output given in response to an ambiguous object name has been\n improved.\n source: \n\n\n* tl/ls-tree-oid-only (2022-01-13) 9 commits\n - ls-tree.c: introduce \"--format\" option\n - cocci: allow padding with `strbuf_addf()`\n - ls-tree.c: introduce struct \"show_tree_data\"\n - ls-tree.c: support --object-only option for \"git-ls-tree\"\n - ls-tree: optimize naming and handling of \"return\" in show_tree()\n - ls-tree: use \"size_t\", not \"int\" for \"struct strbuf\"'s \"len\"\n - ls-tree: use \"enum object_type\", not {blob,tree,commit}_type\n - ls-tree: add missing braces to \"else\" arms\n - ls-tree: remove commented-out code\n\n \"git ls-tree\" learns \"--oid-only\" option, similar to \"--name-only\",\n and more generalized \"--format\" option.\n source: \n\n\n* ab/config-based-hooks-2 (2022-01-07) 17 commits\n (merged to 'next' on 2022-01-19 at 594b6da22c)\n + run-command: remove old run_hook_{le,ve}() hook API\n + receive-pack: convert push-to-checkout hook to hook.h\n + read-cache: convert post-index-change to use hook.h\n + commit: convert {pre-commit,prepare-commit-msg} hook to hook.h\n + git-p4: use 'git hook' to run hooks\n + send-email: use 'git hook run' for 'sendemail-validate'\n + git hook run: add an --ignore-missing flag\n + hooks: convert worktree 'post-checkout' hook to hook library\n + hooks: convert non-worktree 'post-checkout' hook to hook library\n + merge: convert post-merge to use hook.h\n + am: convert applypatch-msg to use hook.h\n + rebase: convert pre-rebase to use hook.h\n + hook API: add a run_hooks_l() wrapper\n + am: convert {pre,post}-applypatch to use hook.h\n + gc: use hook library for pre-auto-gc hook\n + hook API: add a run_hooks() wrapper\n + hook: add 'run' subcommand\n\n More \"config-based hooks\".\n\n Will cook in 'next'.\n source: \n\n\n* jh/builtin-fsmonitor-part2 (2021-12-25) 31 commits\n - fixup! t7527: create test for fsmonitor--daemon\n - fixup! t/perf/p7519: speed up test on Windows\n - t7527: test status with untracked-cache and fsmonitor--daemon\n - fsmonitor: force update index after large responses\n - fsmonitor--daemon: use a cookie file to sync with file system\n - fsmonitor--daemon: periodically truncate list of modified files\n - t/perf/p7519: add fsmonitor--daemon test cases\n - t/perf/p7519: speed up test on Windows\n - t/helper/test-chmtime: skip directories on Windows\n - t/perf: avoid copying builtin fsmonitor files into test repo\n - t7527: create test for fsmonitor--daemon\n - t/helper/fsmonitor-client: create IPC client to talk to FSMonitor Daemon\n - help: include fsmonitor--daemon feature flag in version info\n - fsmonitor--daemon: implement handle_client callback\n - compat/fsmonitor/fsm-listen-darwin: implement FSEvent listener on MacOS\n - compat/fsmonitor/fsm-listen-darwin: add macos header files for FSEvent\n - compat/fsmonitor/fsm-listen-win32: implement FSMonitor backend on Windows\n - fsmonitor--daemon: create token-based changed path cache\n - fsmonitor--daemon: define token-ids\n - fsmonitor--daemon: add pathname classification\n - fsmonitor--daemon: implement 'start' command\n - fsmonitor--daemon: implement 'run' command\n - compat/fsmonitor/fsm-listen-darwin: stub in backend for Darwin\n - compat/fsmonitor/fsm-listen-win32: stub in backend for Windows\n - fsmonitor--daemon: implement 'stop' and 'status' commands\n - fsmonitor--daemon: add a built-in fsmonitor daemon\n - fsmonitor: document builtin fsmonitor\n - fsmonitor: use IPC to query the builtin FSMonitor daemon\n - fsmonitor: config settings are repository-specific\n - fsmonitor-ipc: create client routines for git-fsmonitor--daemon\n - fsmonitor: enhance existing comments\n\n Built-in fsmonitor (part 2).\n\n Expecting a reroll.\n Seems that the discussion stalled.\n cf. \n source: \n\n\n* es/superproject-aware-submodules (2021-11-18) 5 commits\n - submodule: use config to find superproject worktree\n - submodule: record superproject gitdir during 'update'\n - submodule: record superproject gitdir during absorbgitdirs\n - introduce submodule.superprojectGitDir record\n - t7400-submodule-basic: modernize inspect() helper\n\n A configuration variable in a submodule points at the location of\n the superproject it is bound to (RFC).\n\n Expecting a reroll.\n cf. <20211117234300.2598132-1-jonathantanmy@google.com>\n source: <20211117005701.371808-1-emilyshaffer@google.com>\n\n\n* ab/only-single-progress-at-once (2022-01-07) 7 commits\n - *.c: use isatty(0|2), not isatty(STDIN_FILENO|STDERR_FILENO)\n - pack-bitmap-write.c: don't return without stop_progress()\n - progress.c: add temporary variable from progress struct\n - progress.c tests: test some invalid usage\n - progress.c tests: make start/stop commands on stdin\n - progress.c test helper: add missing braces\n - leak tests: fix a memory leak in \"test-progress\" helper\n\n Further tweaks on progress API.\n\n Getting there.\n source: \n\n--------------------------------------------------\n[Discarded]\n\n* ms/customizable-ident-expansion (2021-12-25) 2 commits\n . fixup! keyword expansion: make \"$Id$\" string configurable\n . keyword expansion: make \"$Id$\" string configurable\n\n Instead of \"$Id$\", user-specified string (like $FreeBSD$) can be\n used as an in-blob placeholder for keyword expansion.\n\n Will discard.\n Stalled for too long.\n cf. \n cf. <211101.86fssf3bn3.gmgdl@evledraar.gmail.com>\n source: \n\n\n* tb/cruft-packs (2021-11-29) 17 commits\n . sha1-file.c: don't freshen cruft packs\n . builtin/gc.c: conditionally avoid pruning objects via loose\n . builtin/repack.c: add cruft packs to MIDX during geometric repack\n . builtin/repack.c: use named flags for existing_packs\n . builtin/repack.c: allow configuring cruft pack generation\n . builtin/repack.c: support generating a cruft pack\n . builtin/pack-objects.c: --cruft with expiration\n . reachable: report precise timestamps from objects in cruft packs\n . reachable: add options to add_unseen_recent_objects_to_traversal\n . builtin/pack-objects.c: --cruft without expiration\n . builtin/pack-objects.c: return from create_object_entry()\n . t/helper: add 'pack-mtimes' test-tool\n . pack-mtimes: support writing pack .mtimes files\n . chunk-format.h: extract oid_version()\n . pack-write: pass 'struct packing_data' to 'stage_tmp_packfiles'\n . pack-mtimes: support reading .mtimes files\n . Documentation/technical: add cruft-packs.txt\n\n Instead of leaving unreachable objects in loose form when packing,\n or ejecting them into loose form when repacking, gather them in a\n packfile with an auxiliary file that records the last-use time of\n these objects.\n\n Dropped per author request.\n cf. \n cf. <865b99dd-0b18-9a07-49c1-3959a777c685@gmail.com>\n cf. \n cf. \n source: \n"},{"id":"446545","messageId":"CAFQ2z_PA4zHV8xc1f+sMW9DnaF1E4AQrvkCav_Sx-bKRkgDLtw@mail.gmail.com","threadId":"57273","inReplyTo":"xmqqwnivjgtg.fsf@gitster.g","subject":"Re: What's cooking in git.git (Jan 2022, #05; Wed, 19)","fromName":"Han-Wen Nienhuys","fromEmail":"hanwen@google.com","sentAt":"2022-01-20T10:35:59Z","receivedAt":"2022-01-20T10:36:14Z","isPatch":false,"sender":{"key":"hanwen@google.com","avatar":"https://avatars.githubusercontent.com/u/31547?v=4"},"body":"On Thu, Jan 20, 2022 at 3:12 AM Junio C Hamano wrote:\n> * hn/reftable-coverity-fixes (2021-12-22) 18 commits\n> - reftable: be more paranoid about 0-length memcpy calls\n> - reftable: add print functions to the record types\n..\n> Expecting a reroll.\n\nThe reroll was sent on Jan 12. I dropped the \"reftable: be more\nparanoid about 0-length memcpy calls\" from the series.\n\nShould I send it again?\n\n-- \nHan-Wen Nienhuys - Google Munich\nI work 80%. Don't expect answers from me on Fridays.\n--\nGoogle Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich\nRegistergericht und -nummer: Hamburg, HRB 86891\nSitz der Gesellschaft: Hamburg\nGeschäftsführer: Paul Manicle, Halimah DeLaine Prado\n"},{"id":"446546","messageId":"CAPc5daVFUoK1UQUO5jdsLSUQ8XfkiEk+MoWKg2CZB0=N6N9XXg@mail.gmail.com","threadId":"57273","inReplyTo":"CAFQ2z_PA4zHV8xc1f+sMW9DnaF1E4AQrvkCav_Sx-bKRkgDLtw@mail.gmail.com","subject":"Re: What's cooking in git.git (Jan 2022, #05; Wed, 19)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-01-20T10:44:36Z","receivedAt":"2022-01-20T10:44:53Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"> > * hn/reftable-coverity-fixes (2021-12-22) 18 commits\n> > - reftable: be more paranoid about 0-length memcpy calls\n> > - reftable: add print functions to the record types\n> ..\n> > Expecting a reroll.\n>\n> The reroll was sent on Jan 12. I dropped the \"reftable: be more\n> paranoid about 0-length memcpy calls\" from the series.\n\nThe last time you mentioned \"Jan 12\", I went back to the lore archive\nfor the original thread [1] and didn't find anything but a few comment\nmessages on that day.\n\nThe Message-ID or lore URL would help locate them.\n\nThanks.\n\n[1] https://lore.kernel.org/git/pull.1152.v5.git.git.1640199396.gitgitgadget@gmail.com/\n"},{"id":"446547","messageId":"CAFQ2z_NZL+8No44863K5n7cQkHmtn35_BtKKTQiFzHweHfTHag@mail.gmail.com","threadId":"57273","inReplyTo":"CAPc5daVFUoK1UQUO5jdsLSUQ8XfkiEk+MoWKg2CZB0=N6N9XXg@mail.gmail.com","subject":"Re: What's cooking in git.git (Jan 2022, #05; Wed, 19)","fromName":"Han-Wen Nienhuys","fromEmail":"hanwen@google.com","sentAt":"2022-01-20T11:03:57Z","receivedAt":"2022-01-20T11:04:30Z","isPatch":false,"sender":{"key":"hanwen@google.com","avatar":"https://avatars.githubusercontent.com/u/31547?v=4"},"body":"On Thu, Jan 20, 2022 at 11:44 AM Junio C Hamano wrote:\n>\n> > > * hn/reftable-coverity-fixes (2021-12-22) 18 commits\n> > > - reftable: be more paranoid about 0-length memcpy calls\n> > > - reftable: add print functions to the record types\n> > ..\n> > > Expecting a reroll.\n> >\n> > The reroll was sent on Jan 12. I dropped the \"reftable: be more\n> > paranoid about 0-length memcpy calls\" from the series.\n>\n> The last time you mentioned \"Jan 12\", I went back to the lore archive\n> for the original thread [1] and didn't find anything but a few comment\n> messages on that day.\n\nSorry, you're right. I didn't understand your previous message on the subject.\n\nGGG has started enforcing line wrapping commit messages at 60-76 chars\n(https://github.com/git/git/pull/1152#issuecomment-1011290837). I\nhadn't realized it didn't send out the series.\n\nI grepped for '76' in Documentation/*, but couldn't find any note. Is\nthis new requirement for GGG documented somewhere?\n\n-- \nHan-Wen Nienhuys - Google Munich\nI work 80%. Don't expect answers from me on Fridays.\n--\n\nGoogle Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich\n\nRegistergericht und -nummer: Hamburg, HRB 86891\n\nSitz der Gesellschaft: Hamburg\n\nGeschäftsführer: Paul Manicle, Halimah DeLaine Prado\n"},{"id":"446578","messageId":"CAFQ2z_Pquzt_L6uB6eW1U=aQYm0wCD326xCACW4Mqv_cFtpC-Q@mail.gmail.com","threadId":"57273","inReplyTo":"CAFQ2z_NZL+8No44863K5n7cQkHmtn35_BtKKTQiFzHweHfTHag@mail.gmail.com","subject":"Re: What's cooking in git.git (Jan 2022, #05; Wed, 19)","fromName":"Han-Wen Nienhuys","fromEmail":"hanwen@google.com","sentAt":"2022-01-20T15:14:54Z","receivedAt":"2022-01-20T15:15:08Z","isPatch":false,"sender":{"key":"hanwen@google.com","avatar":"https://avatars.githubusercontent.com/u/31547?v=4"},"body":"On Thu, Jan 20, 2022 at 12:03 PM Han-Wen Nienhuys wrote:\n> > > > * hn/reftable-coverity-fixes (2021-12-22) 18 commits\n> > > > - reftable: be more paranoid about 0-length memcpy calls\n> > > > - reftable: add print functions to the record types\n> > > ..\n> > > > Expecting a reroll.\n> > >\n> > > The reroll was sent on Jan 12. I dropped the \"reftable: be more\n> > > paranoid about 0-length memcpy calls\" from the series.\n> >\n> > The last time you mentioned \"Jan 12\", I went back to the lore archive\n> > for the original thread [1] and didn't find anything but a few comment\n> > messages on that day.\n>\n> Sorry, you're right. I didn't understand your previous message on the subject.\n\nv6 is pull.1152.v6.git.git.1642691534.gitgitgadget@gmail.com\n\n-- \nHan-Wen Nienhuys - Google Munich\nI work 80%. Don't expect answers from me on Fridays.\n--\nGoogle Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich\nRegistergericht und -nummer: Hamburg, HRB 86891\nSitz der Gesellschaft: Hamburg\nGeschäftsführer: Paul Manicle, Halimah DeLaine Prado\n"}]}