{"thread":{"id":"54853","subject":"What's cooking in git.git (Dec 2020, #03; Fri, 18)","startedAt":"2020-12-19T05:35:44Z","lastAt":"2020-12-22T10:23:41Z","messageCount":14,"participants":["Junio C Hamano","Eric Sunshine","Felipe Contreras","Elijah Newren","Han-Wen Nienhuys"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"412622","messageId":"xmqq7dpeqrz4.fsf@gitster.c.googlers.com","threadId":"54853","inReplyTo":null,"subject":"What's cooking in git.git (Dec 2020, #03; Fri, 18)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2020-12-19T05:34:23Z","receivedAt":"2020-12-19T05:35:44Z","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.  Commits prefixed with '-' are\nonly in 'seen' (formerly 'pu'---proposed updates) while commits prefixed\nwith '+' are in 'next'.  The ones marked with '.' do not appear in any of\nthe integration branches, but I am still holding onto them.\n\nA release candidate 2.30-rc1 has been tagged; there are too many\ntopics in flight, sadly many of which haven't been adequately\nreviewed.  I think there are a couple of topics left in 'next' that\nare obvious candidates for the final, but it would be lovely if we\ncan figure out how to get topics in 'seen' that haven't got enough\nlove unstuck.\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* ab/unreachable-break (2020-12-15) 1 commit\n  (merged to 'next' on 2020-12-17 at 3eab6be401)\n + style: do not \"break\" in switch() after \"return\"\n\n Code clean-up.\n\n\n* dd/doc-p4-requirements-update (2020-12-14) 1 commit\n  (merged to 'next' on 2020-12-17 at 59649dd9a8)\n + doc: mention Python 3.x supports\n\n Doc update.\n\n\n* es/perf-export-fix (2020-12-16) 1 commit\n  (merged to 'next' on 2020-12-17 at 57489420ed)\n + t/perf: fix test_export() failure with BSD `sed`\n\n Dev-support fix for BSD.\n\n\n* jb/midx-doc-update (2020-12-14) 1 commit\n  (merged to 'next' on 2020-12-14 at 880b50e89d)\n + docs: multi-pack-index: remove note about future 'verify' work\n\n Doc update.\n\n\n* jc/compat-util-setitimer-fix (2020-12-15) 1 commit\n  (merged to 'next' on 2020-12-17 at 99a9af5066)\n + compat-util: pretend that stub setitimer() always succeeds\n\n Fix a recent bug in a rarely used replacement code.\n\n\n* jc/diff-I-status-fix (2020-12-16) 1 commit\n  (merged to 'next' on 2020-12-17 at d7cd43984a)\n + diff: correct interaction between --exit-code and -I<pattern>\n\n \"git diff -I<pattern> -exit-code\" should exit with 0 status when\n all the changes match the ignored pattern, but it didn't.\n\n\n* jc/strmap-remove-typefix (2020-12-15) 1 commit\n  (merged to 'next' on 2020-12-17 at e94fef7216)\n + strmap: make callers of strmap_remove() to call it in void context\n\n C-std compliance fix.\n\n\n* jh/index-v2-doc-on-fsmn (2020-12-14) 1 commit\n  (merged to 'next' on 2020-12-14 at bd3507ccc8)\n + index-format.txt: document v2 format of file system monitor extension\n\n Doc update.\n\n\n* jk/oid-array-cleanup (2020-12-07) 9 commits\n  (merged to 'next' on 2020-12-14 at 362f6f2618)\n + commit-graph: use size_t for array allocation and indexing\n + commit-graph: replace packed_oid_list with oid_array\n + commit-graph: drop count_distinct_commits() function\n + oid-array: provide a for-loop iterator\n + oid-array: make sort function public\n + cache.h: move hash/oid functions to hash.h\n + t0064: make duplicate tests more robust\n + t0064: drop sha1 mention from filename\n + oid-array.h: drop sha1 mention from header guard\n\n Code clean-up.\n\n\n* js/init-defaultbranch-advice (2020-12-13) 4 commits\n  (merged to 'next' on 2020-12-15 at bcca948854)\n + init: provide useful advice about init.defaultBranch\n + get_default_branch_name(): prepare for showing some advice\n + branch -m: allow renaming a yet-unborn branch\n + init: document `init.defaultBranch` better\n\n Our users are going to be trained to prepare for future change of\n init.defaultBranch configuration variable.\n\n\n* js/t6300-hardcode-main (2020-12-07) 1 commit\n  (merged to 'next' on 2020-12-14 at 4eed7c6a8b)\n + t6300: avoid using the default name of the initial branch\n\n Test update.\n\n\n* js/t7064-master-to-initial (2020-12-08) 1 commit\n  (merged to 'next' on 2020-12-14 at b75529f792)\n + t7064: avoid relying on a specific default branch name\n\n Test update.\n\n\n* js/t7900-protect-pwd-in-config-get (2020-12-09) 1 commit\n  (merged to 'next' on 2020-12-14 at 61ff5e9b5b)\n + t7900: use --fixed-value in git-maintenance tests\n\n Hotfix for test breakage.\n\n\n* rb/nonstop-config-mak-uname-update (2020-12-16) 1 commit\n  (merged to 'next' on 2020-12-17 at 456a1bc21e)\n + config.mak.uname: remove old NonStop compatibility settings\n\n Build update.\n\n\n* rj/make-clean (2020-12-08) 5 commits\n  (merged to 'next' on 2020-12-14 at 767b1398d7)\n + Makefile: don't use a versioned temp distribution directory\n + Makefile: don't try to clean old debian build product\n + gitweb/Makefile: conditionally include ../GIT-VERSION-FILE\n + Documentation/Makefile: conditionally include ../GIT-VERSION-FILE\n + Documentation/Makefile: conditionally include doc.dep\n\n Build optimization.\n\n\n* tb/partial-clone-filters-fix (2020-12-03) 2 commits\n  (merged to 'next' on 2020-12-14 at d44e5942da)\n + upload-pack.c: don't free allowed_filters util pointers\n + builtin/clone.c: don't ignore transport_fetch_refs() errors\n\n Fix potential server side resource deallocation issues when\n responding to a partial clone request.\n\n--------------------------------------------------\n[New Topics]\n\n* jc/config-pretend-gitdir (2020-12-15) 1 commit\n - config: --pretend-git-dir for includeIf:gitdir\n\n WIP\n\n\n* jc/deprecate-pack-redundant (2020-12-15) 1 commit\n - pack-redundant: gauge the usage before proposing its removal\n\n Warn loudly when the \"pack-redundant\" command, which has been left\n stale with almost unusable performance issues, gets used, as we no\n longer want to recommend its use (instead just \"repack -d\" instead).\n\n\n* en/merge-ort-recursive (2020-12-16) 4 commits\n - merge-ort: implement merge_incore_recursive()\n - merge-ort: make clear_internal_opts() aware of partial clearing\n - merge-ort: copy a few small helper functions from merge-recursive.c\n - commit: move reverse_commit_list() from merge-recursive\n (this branch uses en/merge-ort-2 and en/merge-ort-impl; is tangled with en/merge-ort-3.)\n\n The ORT merge strategy learned to synthesize virtual ancestor tree\n by recursively merging multiple merge bases together, just like the\n recursive backend has done for years.\n\n Will merge to 'next'.\n\n\n* js/no-more-prepare-for-main-in-test (2020-12-16) 11 commits\n  (merged to 'next' on 2020-12-18 at d15a382d4d)\n + tests: drop the `PREPARE_FOR_MAIN_BRANCH` prereq\n + t9902: use `main` as initial branch name\n + t6302: use `main` as initial branch name\n + t5703: use `main` as initial branch name\n + t5510: use `main` as initial branch name\n + t5505: finalize transitioning to using the branch name `main`\n + t3205: finalize transitioning to using the branch name `main`\n + t3203: complete the transition to using the branch name `main`\n + t3201: finalize transitioning to using the branch name `main`\n + t3200: finish transitioning to the initial branch name `main`\n + t1400: use `main` as initial branch name\n\n Test coverage fix.\n\n Will merge to 'master'.\n\n\n* jx/pack-redundant-on-single-pack (2020-12-16) 1 commit\n  (merged to 'next' on 2020-12-18 at b819311529)\n + pack-redundant: fix crash when one packfile in repo\n\n \"git pack-redandant\" when there is only one packfile used to crash,\n which has been corrected.\n\n Will merge to 'master'.\n\n--------------------------------------------------\n[Stalled]\n\n* ak/corrected-commit-date (2020-10-08) 10 commits\n - doc: add corrected commit date info\n - commit-reach: use corrected commit dates in paint_down_to_common()\n - commit-graph: use generation v2 only if entire chain does\n - commit-graph: implement generation data chunk\n - commit-graph: implement corrected commit date\n - commit-graph: add a slab to store topological levels\n - commit-graph: return 64-bit generation number\n - commit-graph: consolidate fill_commit_graph_info\n - revision: parse parent in indegree_walk_step()\n - commit-graph: fix regression when computing Bloom filters\n\n The commit-graph learned to use corrected commit dates instead of\n the generation number to help topological revision traversal.\n\n Getting there.\n cf. <85y2jiqq3c.fsf@gmail.com>\n cf. <685afed6-f01f-5d22-80d4-00fdc11caf0a@gmail.com>\n cf. <20201103053629.GA13228@Abhishek-Arch>\n\n\n* mt/grep-sparse-checkout (2020-12-06) 10 commits\n - t7817: do not depend on any specific default branch name\n - config: add setting to ignore sparsity patterns in some cmds\n - grep: honor sparse checkout patterns\n - config: correctly read worktree configs in submodules\n - config: make do_git_config_sequence receive a 'struct repository'\n - t/helper/test-config: unify exit labels\n - t/helper/test-config: diagnose missing arguments\n - t/helper/test-config: be consistent with exit codes\n - t1308-config-set: avoid false positives when using test-config\n - doc: grep: unify info on configuration variables\n (this branch is used by mt/rm-sparse-checkout.)\n\n \"git grep\" has been tweaked to be limited to the sparse checkout\n paths.\n\n\n* mt/rm-sparse-checkout (2020-12-08) 1 commit\n - rm: honor sparse checkout patterns\n (this branch uses mt/grep-sparse-checkout.)\n\n \"git rm\" follows suit to \"git grep\" to ignore paths outside the\n sparsity pattern when the sparse checkout feature is in use.\n\n Need to wait for how these fit in larger picture.\n cf. <CABPp-BGMX3wb7LiS1HkJpGveoW3J1oR0vVHbKTF5+qYLRF+59g@mail.gmail.com>\n\n\n* jk/symlinked-dotgitx-files (2020-10-23) 9 commits\n  (merged to 'next' on 2020-10-26 at c1dd37b024)\n + docs: document symlink restrictions for .git* files\n + fsck: complain when .gitattributes or .gitignore is a symlink\n + verify_path(): disallow symlinks in .gitattributes and .gitignore\n + t0060: test obscured .gitattributes and .gitignore matching\n + t7450: test .gitmodules symlink matching against obscured names\n + t7450: test verify_path() handling of gitmodules\n + t7415: rename to expand scope\n + fsck_tree(): wrap some long lines\n + fsck_tree(): fix shadowed variable\n\n Originally merged to 'next' on 2020-10-23\n\n \"git fsck\" and the corresponding check done during the transport\n learned to ensure that in-tree files like `.gitignore` and\n `.gitattributes` are not symbolic links.\n\n It seems that there are real projects with .gitignore recorded as\n symlinks, which may need to loosen the fsck setting.  Do we need to\n introduce a class that is separate from symlinked .gitmodules that\n probably is with potential consequences that is more/less grave?\n\n\n* sm/curl-retry (2020-10-13) 3 commits\n - http: automatically retry some requests\n - replace CURLOPT_FILE With CURLOPT_WRITEDATA\n - remote-curl: add testing for intelligent retry for HTTP\n\n The http transport has been taught to retry a failed request that\n may reasonably be retried.\n\n Expecting a reroll.\n cf. <20201015000410.GB328643@google.com>\n cf. <CAM4o00eefXK2CJ_FxwwVPpBKL01JsJANf+SdjCtw_0NVV82L+Q@mail.gmail.com>\n\n\n* sv/t7001-modernize (2020-09-25) 11 commits\n - t7001: move cleanup code from outside the tests into them\n - t7001: use `test` rather than `[`\n - t7001: use here-docs instead of echo\n - t7001: put each command on a separate line\n - t7001: use ': >' rather than 'touch'\n - t7001: change (cd <path> && git foo) to (git -C <path> foo)\n - t7001: remove whitespace after redirect operators\n - t7001: change the style for cd according to subshell\n - t7001: remove unnecessary blank lines\n - t7001: use TAB instead of spaces\n - t7001: convert tests from the old style to the current style\n\n Test script modernization.\n\n Expecting a reroll.\n cf. <20200925170256.11490-1-shubhunic@gmail.com>\n\n\n* ew/decline-core-abbrev (2020-09-01) 1 commit\n - core.abbrev <off|false|no> disables abbreviations\n\n Allow the configuration to specify no abbreviation regardless of\n the hash algorithm.\n\n Expecting a reroll.  The intent is very good.\n\n\n* ar/fetch-transfer-ipversion (2020-09-16) 1 commit\n - config: option transfer.ipversion to set transport protocol version for network fetches\n\n Adds transfer.ipversion configuration variable.\n\n Needs more work.\n\n\n* vv/send-email-with-less-secure-apps-access (2020-08-29) 1 commit\n - Documentation/git-send-email.txt: Mention less secure app access might need to enable.\n\n Doc update.\n\n Expecting a reroll.\n cf. <xmqqwo1hi9nv.fsf@gitster.c.googlers.com>\n cf. <xmqqft85i72s.fsf@gitster.c.googlers.com>\n\n\n* jc/war-on-dashed-git (2020-08-27) 1 commit\n - git: catch an attempt to run \"git-foo\"\n\n The first step to remove on-disk binaries for built-in subcommands\n by soliciting objections.\n\n On hold for now.\n\n\n* dr/push-remoteref-fix (2020-04-23) 1 commit\n - remote.c: fix handling of %(push:remoteref)\n\n The \"%(push:remoteref)\" placeholder in the \"--format=\" argument of\n \"git format-patch\" (and friends) only showed what got explicitly\n configured, not what ref at the receiving end would be updated when\n \"git push\" was used, as it ignored the default behaviour (e.g. update\n the same ref as the source).\n\n Discard for now.\n cf. <xmqqv9gu7c61.fsf@gitster.c.googlers.com>\n cf. <20200911214358.acl3hy2e763begoo@feanor>\n\n\n* mk/use-size-t-in-zlib (2018-10-15) 1 commit\n - zlib.c: use size_t for size\n\n The wrapper to call into zlib followed our long tradition to use\n \"unsigned long\" for sizes of regions in memory, which have been\n updated to use \"size_t\".\n\n--------------------------------------------------\n[Needs Review]\n\n* ss/submodule-add-in-c (2020-12-15) 3 commits\n - t7400: add test to check 'submodule add' for tracked paths\n - submodule: port submodule subcommand 'add' from shell to C\n - dir: change the scope of function 'directory_exists_in_index()'\n\n \"git submodule add\" being rewritten in C.\n\n Needs review.\n\n\n* fc/bash-completion-post-2.29 (2020-11-10) 26 commits\n - completion: bash: shuffle __gitcomp functions\n - completion: bash: cleanup __gitcomp* invocations\n - completion: bash: add __gitcomp_opts\n - completion: bash: improve __gitcomp description\n - completion: bash: rename _get_comp_words_by_ref()\n - completion: bash: trivial cleanup\n - completion: bash: cleanup _get_comp_words_by_ref()\n - completion: bash: refactor _get_comp_words_by_ref()\n - completion: bash: simplify _get_comp_words_by_ref()\n - test: completion: switch __gitcomp_nl prefix test\n - completion: bash: simplify config_variable_name\n - completion: bash: improve __gitcomp suffix code\n - completion: bash: change suffix check in __gitcomp\n - completion: bash: simplify __gitcomp\n - completion: bash: refactor __gitcomp\n - completion: bash: simplify equal suffix check\n - completion: bash: factor out check in __gitcomp\n - completion: bash: get rid of any non-append code\n - completion: bash: get rid of _append() functions\n - completion: bash: remove non-append functionality\n - test: completion: add run_func() helper\n - test: completion: fix currently typed words\n - completion: bash: do not modify COMP_WORDBREAKS\n - completion: bash: fix for suboptions with value\n - completion: bash: add correct suffix in variables\n - completion: bash: fix prefix detection in branch.*\n\n Needs review.\n\n\n* ag/merge-strategies-in-c (2020-11-24) 13 commits\n - sequencer: use the \"octopus\" merge strategy without forking\n - sequencer: use the \"resolve\" strategy without forking\n - merge: use the \"octopus\" strategy without forking\n - merge: use the \"resolve\" strategy without forking\n - merge-octopus: rewrite in C\n - merge-recursive: move better_branch_name() to merge.c\n - merge-resolve: rewrite in C\n - merge-index: don't fork if the requested program is `git-merge-one-file'\n - merge-index: libify merge_one_path() and merge_all()\n - merge-one-file: rewrite in C\n - update-index: move add_cacheinfo() to read-cache.c\n - t6060: modify multiple files to expose a possible issue with merge-index\n - t6407: modernise tests\n\n The resolve and octopus merge strategy backends have been rewritten\n in C.\n\n Needs review.\n\n--------------------------------------------------\n[Cooking]\n\n* mt/parallel-checkout-part-1 (2020-12-16) 9 commits\n - entry: add checkout_entry_ca() taking preloaded conv_attrs\n - entry: move conv_attrs lookup up to checkout_entry()\n - entry: extract update_ce_after_write() from write_entry()\n - entry: make fstat_output() and read_blob_entry() public\n - entry: extract a header file for entry.c functions\n - convert: add classification for conv_attrs struct\n - convert: add get_stream_filter_ca() variant\n - convert: add [async_]convert_to_working_tree_ca() variants\n - convert: make convert_attrs() and convert structs public\n\n Parallel checkout.\n\n Looking good.\n\n\n* en/merge-ort-3 (2020-12-15) 11 commits\n - merge-ort: add implementation of type-changed rename handling\n - merge-ort: add implementation of normal rename handling\n - merge-ort: add implementation of rename collisions\n - merge-ort: add implementation of rename/delete conflicts\n - merge-ort: add implementation of both sides renaming differently\n - merge-ort: add implementation of both sides renaming identically\n - merge-ort: add basic outline for process_renames()\n - merge-ort: implement compare_pairs() and collect_renames()\n - merge-ort: implement detect_regular_renames()\n - merge-ort: add initial outline for basic rename detection\n - merge-ort: add basic data structures for handling renames\n (this branch uses en/merge-ort-2 and en/merge-ort-impl; is tangled with en/merge-ort-recursive.)\n\n Rename detection is added to the \"ORT\" merge strategy.\n\n\n* jk/disambiguate-equal-in-config-param (2020-12-09) 3 commits\n - config: store \"git -c\" variables using more robust format\n - config: parse more robust format in GIT_CONFIG_PARAMETERS\n - quote: make sq_dequote_step() a public function\n (this branch uses ps/config-env-pairs.)\n\n The quoting rules used to pass \"git -c var=val\" configuration\n across processes have been updated in a backward compatible way, so\n that the value read from an environment variable can contain an\n equal sign when using the \"git --config-env var=env\" feature.\n\n We may want to make this just a middle part of the\n ps/config-env-pairs topic with a bit of patch shuffling.\n\n\n* ps/config-env-pairs (2020-12-09) 6 commits\n - config: allow specifying config entries via envvar pairs\n - config: refactor parsing of GIT_CONFIG_PARAMETERS\n - config: extract function to parse config pairs\n - environment: make `getenv_safe()` non-static\n - config: add new way to pass config via `--config-env`\n - git: add `--super-prefix` to usage string\n (this branch is used by jk/disambiguate-equal-in-config-param.)\n\n Introduce two new ways to feed configuration variable-value pairs\n via environment variables.\n\n\n* bc/hashed-mailmap (2020-12-12) 1 commit\n - mailmap: support hashed entries in mailmaps\n\n The mailmap database learned to take hashed value as the original\n side of mapping.\n\n Expecting a reroll.\n\n\n* so/log-diff-merge (2020-12-16) 33 commits\n - t4013: add tests for --diff-merges=first-parent\n - doc/git-show: include --diff-merges description\n - doc/rev-list-options: document --first-parent changes merges format\n - doc/diff-generate-patch: mention new --diff-merges option\n - doc/git-log: describe new --diff-merges options\n - diff-merges: add '--diff-merges=1' as synonym for 'first-parent'\n - diff-merges: add old mnemonic counterparts to --diff-merges\n - diff-merges: let new options enable diff without -p\n - diff-merges: do not imply -p for new options\n - diff-merges: handle imply -p on -c/--cc logic for log.c\n - diff-merges: fix style of functions definitions\n - diff-merges: implement new values for --diff-merges\n - diff-merges: make -m/-c/--cc explicitly mutually exclusive\n - diff-merges: refactor opt settings into separate functions\n - diff-merges: get rid of now empty diff_merges_init_revs()\n - diff-merges: group diff-merge flags next to each other inside 'rev_info'\n - diff-merges: split 'ignore_merges' field\n - diff-merges: fix -m to properly override -c/--cc\n - t4013: add tests for -m failing to override -c/--cc\n - t4013: support test_expect_failure through ':failure' magic\n - diff-merges: revise revs->diff flag handling\n - diff-merges: introduce revs->first_parent_merges flag\n - diff-merges: new function diff_merges_set_dense_combined_if_unset()\n - diff-merges: new function diff_merges_suppress()\n - diff-merges: re-arrange functions to match the order they are called in\n - diff-merges: rename diff_merges_default_to_enable() to match semantics\n - diff-merges: move checks for first_parent_only out of the module\n - diff-merges: rename all functions to have common prefix\n - revision: move diff merges functions to its own diff-merges.c\n - revision: provide implementation for diff merges tweaks\n - revision: factor out initialization of diff-merge related settings\n - revision: factor out setup of diff-merge related settings\n - revision: factor out parsing of diff-merge related options\n\n \"git log\" learned a new \"--diff-merges=<how>\" option.\n\n Rerolled.\n\n\n* bc/rev-parse-path-format (2020-12-12) 2 commits\n - rev-parse: add option for absolute or relative path formatting\n - abspath: add a function to resolve paths with missing components\n\n \"git rev-parse\" can be explicitly told to give output as absolute\n or relative path.\n\n\n* en/merge-ort-impl (2020-12-13) 21 commits\n - merge-ort: free data structures in merge_finalize()\n - merge-ort: add implementation of record_conflicted_index_entries()\n - tree: enable cmp_cache_name_compare() to be used elsewhere\n - merge-ort: add implementation of checkout()\n - merge-ort: basic outline for merge_switch_to_result()\n - merge-ort: step 3 of tree writing -- handling subdirectories as we go\n - merge-ort: step 2 of tree writing -- function to create tree object\n - merge-ort: step 1 of tree writing -- record basenames, modes, and oids\n - merge-ort: have process_entries operate in a defined order\n - merge-ort: add a preliminary simple process_entries() implementation\n - merge-ort: avoid recursing into identical trees\n - merge-ort: record stage and auxiliary info for every path\n - merge-ort: compute a few more useful fields for collect_merge_info\n - merge-ort: avoid repeating fill_tree_descriptor() on the same tree\n - merge-ort: implement a very basic collect_merge_info()\n - merge-ort: add an err() function similar to one from merge-recursive\n - merge-ort: use histogram diff\n - merge-ort: port merge_start() from merge-recursive\n - merge-ort: add some high-level algorithm structure\n - merge-ort: setup basic internal data structures\n - Merge branch 'en/strmap' into en/merge-ort-impl\n (this branch is used by en/merge-ort-2, en/merge-ort-3 and en/merge-ort-recursive.)\n\n The merge backend \"done right\" starts to emerge.\n\n Will merge to 'next'.\n\n\n* es/config-hooks (2020-12-07) 34 commits\n . run-command: stop thinking about hooks\n . receive-pack: convert receive hooks to hook.h\n . post-update: use hook.h library\n . proc-receive: acquire hook list from hook.h\n . receive-pack: convert 'update' hook to hook.h\n . reference-transaction: look for hooks in config\n . transport: convert pre-push hook to use config\n . hook: convert 'post-rewrite' hook to config\n . hooks: convert 'post-checkout' hook to hook library\n . git-p4: use 'git hook' to run hooks\n . receive-pack: convert push-to-checkout hook to hook.h\n . read-cache: convert post-index-change hook to use config\n . rebase: teach pre-rebase to use hook.h\n . gc: use hook library for pre-auto-gc hook\n . merge: use config-based hooks for post-merge hook\n . am: convert applypatch hooks to use config\n . commit: use config-based hooks\n . hooks: allow callers to capture output\n . run-command: allow capturing of collated output\n . hook: provide stdin by string_list or callback\n . run-command: add stdin callback for parallelization\n . hook: allow specifying working directory for hooks\n . hook: allow parallel hook execution\n . run-command: allow stdin for run_processes_parallel\n . hook: support passing stdin to hooks\n . hook: replace find_hook() with hook_exists()\n . hook: add 'run' subcommand\n . parse-options: parse into strvec\n . hook: implement hookcmd.<name>.skip\n . hook: respect hook.runHookDir\n . hook: include hookdir hook in list\n . hook: add list command\n . hook: scaffolding for git-hook subcommand\n . doc: propose hooks managed by the config\n\n The \"hooks defined in config\" topic.\n\n Ejected for now, as it has been breaking the tip of 'seen' for too\n long.\n\n\n* hn/reftable (2020-12-09) 15 commits\n . Add \"test-tool dump-reftable\" command.\n . git-prompt: prepare for reftable refs backend\n . Reftable support for git-core\n . reftable: rest of library\n . reftable: reftable file level tests\n . reftable: read reftable files\n . reftable: write reftable files\n . reftable: a generic binary tree implementation\n . reftable: reading/writing blocks\n . reftable: (de)serialization for the polymorphic record type.\n . reftable: add blocksource, an abstraction for random access reads\n . reftable: utility functions\n . reftable: add error related functionality\n . reftable: add LICENSE\n . init-db: set the_repository->hash_algo early on\n\n The \"reftable\" backend for the refs API.\n\n Ejected for now, as it has been breaking the tip of 'seen' for too\n long.\n\n\n* ab/mktag (2020-12-09) 11 commits\n - SQUASH???\n - mktag: allow turning off fsck.extraHeaderEntry\n - fsck: make fsck_config() re-usable\n - mktag doc: update to explain why to use this\n - mktag: use fsck instead of custom verify_tag()\n - mktag tests: improve verify_object() test coverage\n - mktag tests: remove needless SHA-1 hardcoding\n - mktag tests: don't needlessly use a subshell\n - mktag: remove redundant braces in one-line body \"if\"\n - mktag: use default strbuf_read() hint\n - mktag doc: say <hash> not <sha1>\n\n \"git mktag\" validates its input using its own rules before writing\n a tag object---it has been updated to share the logic with \"git\n fsck\".\n\n Expecting a reroll, but it seems getting closer.\n\n\n* ab/trailers-extra-format (2020-12-09) 5 commits\n  (merged to 'next' on 2020-12-14 at 9fc731944e)\n + pretty format %(trailers): add a \"key_value_separator\"\n + pretty format %(trailers): add a \"keyonly\"\n + pretty-format %(trailers): fix broken standalone \"valueonly\"\n + pretty format %(trailers) doc: avoid repetition\n + pretty format %(trailers) test: split a long line\n\n The \"--format=%(trailers)\" mechanism gets enhanced to make it\n easier to design output for machine consumption.\n\n Will cook in 'next'.\n\n\n* en/diffcore-rename (2020-12-14) 9 commits\n - diffcore-rename: remove unneccessary duplicate entry checks\n - diffcore-rename: accelerate rename_dst setup\n - diffcore-rename: simplify and accelerate register_rename_src()\n - t4058: explore duplicate tree entry handling in a bit more detail\n - t4058: add more tests and documentation for duplicate tree entry handling\n - diffcore-rename: reduce jumpiness in progress counters\n - diffcore-rename: simplify limit check\n - diffcore-rename: avoid usage of global in too_many_rename_candidates()\n - diffcore-rename: rename num_create to num_destinations\n\n File-level rename detection updates.\n\n\n* en/merge-ort-2 (2020-12-13) 7 commits\n - merge-ort: add modify/delete handling and delayed output processing\n - merge-ort: add die-not-implemented stub handle_content_merge() function\n - merge-ort: add function grouping comments\n - merge-ort: add a paths_to_free field to merge_options_internal\n - merge-ort: add a path_conflict field to merge_options_internal\n - merge-ort: add a clear_internal_opts helper\n - merge-ort: add a few includes\n (this branch is used by en/merge-ort-3 and en/merge-ort-recursive; uses en/merge-ort-impl.)\n\n More \"ORT\" merge strategy.\n\n Will merge to 'next'.\n\n\n* fc/pull-merge-rebase (2020-12-15) 5 commits\n - pull: display default warning only when non-ff\n - pull: correct condition to trigger non-ff advice\n - pull: get rid of unnecessary global variable\n - pull: give the advice for choosing rebase/merge much later\n - pull: refactor fast-forward check\n\n When a user does not tell \"git pull\" to use rebase or merge, the\n command gives a loud message telling a user to choose between\n rebase or merge but creates a merge anyway, forcing users who would\n want to rebase to redo the operation.  Fix an early part of this\n problem by tightening the condition to give the message---there is\n no reason to stop or force the user to choose between rebase or\n merge if the history fast-forwards.\n\n\n* pk/subsub-fetch-fix-take-2 (2020-12-09) 1 commit\n  (merged to 'next' on 2020-12-14 at ccc01a5f66)\n + submodules: fix of regression on fetching of non-init subsub-repo\n\n \"git fetch --recurse-submodules\" fix (second attempt).\n\n Will cook in 'next'.\n\n\n* en/stash-apply-sparse-checkout (2020-12-01) 3 commits\n - stash: fix stash application in sparse-checkouts\n - stash: remove unnecessary process forking\n - t7012: add a testcase demonstrating stash apply bugs in sparse checkouts\n\n \"git stash\" did not work well in a sparsely checked out working\n tree.\n\n\n* tb/pack-bitmap (2020-12-08) 24 commits\n  (merged to 'next' on 2020-12-15 at 773268c2fb)\n + pack-bitmap-write: better reuse bitmaps\n + pack-bitmap-write: relax unique revwalk condition\n + pack-bitmap-write: use existing bitmaps\n + pack-bitmap: factor out 'add_commit_to_bitmap()'\n + pack-bitmap: factor out 'bitmap_for_commit()'\n + pack-bitmap-write: ignore BITMAP_FLAG_REUSE\n + pack-bitmap-write: build fewer intermediate bitmaps\n + pack-bitmap.c: check reads more aggressively when loading\n + pack-bitmap-write: rename children to reverse_edges\n + t5310: add branch-based checks\n + commit: implement commit_list_contains()\n + bitmap: implement bitmap_is_subset()\n + pack-bitmap-write: fill bitmap with commit history\n + pack-bitmap-write: pass ownership of intermediate bitmaps\n + pack-bitmap-write: reimplement bitmap writing\n + ewah: add bitmap_dup() function\n + ewah: implement bitmap_or()\n + ewah: make bitmap growth less aggressive\n + ewah: factor out bitmap growth\n + rev-list: die when --test-bitmap detects a mismatch\n + t5310: drop size of truncated ewah bitmap\n + pack-bitmap: bounds-check size of cache extension\n + pack-bitmap: fix header size check\n + ewah/ewah_bitmap.c: avoid open-coding ALLOC_GROW()\n\n Various improvements to the codepath that writes out pack bitmaps.\n\n Will cook in 'next'.\n\n\n* js/default-branch-name-tests-final-stretch (2020-11-19) 29 commits\n - tests: drop prereq `PREPARE_FOR_MAIN_BRANCH` where no longer needed\n - t99*: adjust the references to the default branch name \"main\"\n - tests(git-p4): transition to the default branch name `main`\n - t9[5-7]*: adjust the references to the default branch name \"main\"\n - t9[0-4]*: adjust the references to the default branch name \"main\"\n - t8*: adjust the references to the default branch name \"main\"\n - t7[5-9]*: adjust the references to the default branch name \"main\"\n - t7[0-4]*: adjust the references to the default branch name \"main\"\n - t6[4-9]*: adjust the references to the default branch name \"main\"\n - t64*: preemptively adjust alignment to prepare for `master` -> `main`\n - t6[0-3]*: adjust the references to the default branch name \"main\"\n - t5[6-9]*: adjust the references to the default branch name \"main\"\n - t55[4-9]*: adjust the references to the default branch name \"main\"\n - t55[23]*: adjust the references to the default branch name \"main\"\n - t551*: adjust the references to the default branch name \"main\"\n - t550*: adjust the references to the default branch name \"main\"\n - t5503: prepare aligned comment for replacing `master` with `main`\n - t5[0-4]*: adjust the references to the default branch name \"main\"\n - t5323: prepare centered comment for `master` -> `main`\n - t4*: adjust the references to the default branch name \"main\"\n - t3[5-9]*: adjust the references to the default branch name \"main\"\n - t34*: adjust the references to the default branch name \"main\"\n - t3416: preemptively adjust alignment in a comment\n - t3[0-3]*: adjust the references to the default branch name \"main\"\n - t2*: adjust the references to the default branch name \"main\"\n - t[01]*: adjust the references to the default branch name \"main\"\n - t0060: preemptively adjust alignment\n - tests: mark tests relying on the current default for `init.defaultBranch`\n - Merge 'jk/diff-release-filespec-fix' into js/default-branch-name-tests-final-stretch\n\n Prepare tests not to be affected by the name of the default branch\n \"git init\" creates.\n\n\n* ds/maintenance-part-4 (2020-12-09) 6 commits\n - t7900: make macOS-specific test work on Windows\n - t7900: fix test failures when invoked individually via --run\n - maintenance: use Windows scheduled tasks\n - maintenance: use launchctl on macOS\n - maintenance: include 'cron' details in docs\n - maintenance: extract platform-specific scheduling\n\n Follow-up on the \"maintenance part-3\" which introduced scheduled\n maintenance tasks to support platforms whose native scheduling\n methods are not 'cron'.\n\n\n* sj/untracked-files-in-submodule-directory-is-not-dirty (2020-12-08) 1 commit\n - diff: do not show submodule with untracked files as \"-dirty\"\n\n \"git diff\" showed a submodule working tree with untracked cruft as\n \"Submodule commit <objectname>-dirty\", but a natural expectation is\n that the \"-dirty\" indicator would align with \"git describe --dirty\",\n which does not consider having untracked files in the working tree\n as source of dirtiness.  The inconsistency has been fixed.\n"},{"id":"412623","messageId":"CAPig+cRycw=JnYOxCspJiLWbX10FK_QJhHx3A98oJBSG_MBaoQ@mail.gmail.com","threadId":"54853","inReplyTo":"xmqq7dpeqrz4.fsf@gitster.c.googlers.com","subject":"Re: What's cooking in git.git (Dec 2020, #03; Fri, 18)","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2020-12-19T06:44:17Z","receivedAt":"2020-12-19T06:45:26Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Sat, Dec 19, 2020 at 12:36 AM Junio C Hamano <gitster@pobox.com> wrote:\n> * ds/maintenance-part-4 (2020-12-09) 6 commits\n>  - t7900: make macOS-specific test work on Windows\n>  - t7900: fix test failures when invoked individually via --run\n>  - maintenance: use Windows scheduled tasks\n>  - maintenance: use launchctl on macOS\n>  - maintenance: include 'cron' details in docs\n>  - maintenance: extract platform-specific scheduling\n>\n>  Follow-up on the \"maintenance part-3\" which introduced scheduled\n>  maintenance tasks to support platforms whose native scheduling\n>  methods are not 'cron'.\n\nI've read this series in its entirety at each re-roll, and am\nsatisfied that the comments from my reviews have been addressed.\n(There may be one or two remaining subjective nits but nothing worth\nholding up the series.)\n"},{"id":"412641","messageId":"5fde09c1ac7d_1def912083c@natae.notmuch","threadId":"54853","inReplyTo":"xmqq7dpeqrz4.fsf@gitster.c.googlers.com","subject":"RE: What's cooking in git.git (Dec 2020, #03; Fri, 18)","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2020-12-19T14:10:09Z","receivedAt":"2020-12-19T14:10:53Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Junio C Hamano wrote:\n> * fc/bash-completion-post-2.29 (2020-11-10) 26 commits\n>  - completion: bash: shuffle __gitcomp functions\n>  - completion: bash: cleanup __gitcomp* invocations\n>  - completion: bash: add __gitcomp_opts\n>  - completion: bash: improve __gitcomp description\n>  - completion: bash: rename _get_comp_words_by_ref()\n>  - completion: bash: trivial cleanup\n>  - completion: bash: cleanup _get_comp_words_by_ref()\n>  - completion: bash: refactor _get_comp_words_by_ref()\n>  - completion: bash: simplify _get_comp_words_by_ref()\n>  - test: completion: switch __gitcomp_nl prefix test\n>  - completion: bash: simplify config_variable_name\n>  - completion: bash: improve __gitcomp suffix code\n>  - completion: bash: change suffix check in __gitcomp\n>  - completion: bash: simplify __gitcomp\n>  - completion: bash: refactor __gitcomp\n>  - completion: bash: simplify equal suffix check\n>  - completion: bash: factor out check in __gitcomp\n>  - completion: bash: get rid of any non-append code\n>  - completion: bash: get rid of _append() functions\n>  - completion: bash: remove non-append functionality\n>  - test: completion: add run_func() helper\n>  - test: completion: fix currently typed words\n>  - completion: bash: do not modify COMP_WORDBREAKS\n>  - completion: bash: fix for suboptions with value\n>  - completion: bash: add correct suffix in variables\n>  - completion: bash: fix prefix detection in branch.*\n> \n>  Needs review.\n\nI think I already mentioned these should be dropped in favor of an\neasier to digest series [1].\n\nI just sent another try as a reminder [2].\n\nCheers.\n\n[1] https://lore.kernel.org/git/20201119015209.1155170-1-felipe.contreras@gmail.com/\n[2] https://lore.kernel.org/git/20201219140621.1961760-1-felipe.contreras@gmail.com/\n\n-- \nFelipe Contreras\n"},{"id":"412651","messageId":"xmqqwnxdpvt0.fsf@gitster.c.googlers.com","threadId":"54853","inReplyTo":"5fde09c1ac7d_1def912083c@natae.notmuch","subject":"Re: What's cooking in git.git (Dec 2020, #03; Fri, 18)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2020-12-19T17:09:15Z","receivedAt":"2020-12-19T17:10:14Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Felipe Contreras <felipe.contreras@gmail.com> writes:\n\n> Junio C Hamano wrote:\n>> * fc/bash-completion-post-2.29 (2020-11-10) 26 commits\n>>  - completion: bash: shuffle __gitcomp functions\n>>  - completion: bash: cleanup __gitcomp* invocations\n>>  - completion: bash: add __gitcomp_opts\n>>  - completion: bash: improve __gitcomp description\n>>  - completion: bash: rename _get_comp_words_by_ref()\n>>  - completion: bash: trivial cleanup\n>>  - completion: bash: cleanup _get_comp_words_by_ref()\n>>  - completion: bash: refactor _get_comp_words_by_ref()\n>>  - completion: bash: simplify _get_comp_words_by_ref()\n>>  - test: completion: switch __gitcomp_nl prefix test\n>>  - completion: bash: simplify config_variable_name\n>>  - completion: bash: improve __gitcomp suffix code\n>>  - completion: bash: change suffix check in __gitcomp\n>>  - completion: bash: simplify __gitcomp\n>>  - completion: bash: refactor __gitcomp\n>>  - completion: bash: simplify equal suffix check\n>>  - completion: bash: factor out check in __gitcomp\n>>  - completion: bash: get rid of any non-append code\n>>  - completion: bash: get rid of _append() functions\n>>  - completion: bash: remove non-append functionality\n>>  - test: completion: add run_func() helper\n>>  - test: completion: fix currently typed words\n>>  - completion: bash: do not modify COMP_WORDBREAKS\n>>  - completion: bash: fix for suboptions with value\n>>  - completion: bash: add correct suffix in variables\n>>  - completion: bash: fix prefix detection in branch.*\n>> \n>>  Needs review.\n>\n> I think I already mentioned these should be dropped in favor of an\n> easier to digest series [1].\n\nThanks.  I didn't even notice these were still in my tree, as these\ndidn't seem to get any attention to those who know/care about\ncompletion.\n\n> I just sent another try as a reminder [2].\n\nWill eject and replace.\n"},{"id":"412653","messageId":"xmqqo8ippvll.fsf@gitster.c.googlers.com","threadId":"54853","inReplyTo":"CAPig+cRycw=JnYOxCspJiLWbX10FK_QJhHx3A98oJBSG_MBaoQ@mail.gmail.com","subject":"Re: What's cooking in git.git (Dec 2020, #03; Fri, 18)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2020-12-19T17:13:42Z","receivedAt":"2020-12-19T17:14:41Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Eric Sunshine <sunshine@sunshineco.com> writes:\n\n> On Sat, Dec 19, 2020 at 12:36 AM Junio C Hamano <gitster@pobox.com> wrote:\n>> * ds/maintenance-part-4 (2020-12-09) 6 commits\n>>  - t7900: make macOS-specific test work on Windows\n>>  - t7900: fix test failures when invoked individually via --run\n>>  - maintenance: use Windows scheduled tasks\n>>  - maintenance: use launchctl on macOS\n>>  - maintenance: include 'cron' details in docs\n>>  - maintenance: extract platform-specific scheduling\n>>\n>>  Follow-up on the \"maintenance part-3\" which introduced scheduled\n>>  maintenance tasks to support platforms whose native scheduling\n>>  methods are not 'cron'.\n>\n> I've read this series in its entirety at each re-roll, and am\n> satisfied that the comments from my reviews have been addressed.\n> (There may be one or two remaining subjective nits but nothing worth\n> holding up the series.)\n\nThanks.\n"},{"id":"412673","messageId":"CABPp-BFoSz40-1mNLrxCgMTccYqLOg6ifX5PeLDutbimF9ysPQ@mail.gmail.com","threadId":"54853","inReplyTo":"xmqq7dpeqrz4.fsf@gitster.c.googlers.com","subject":"Re: What's cooking in git.git (Dec 2020, #03; Fri, 18)","fromName":"Elijah Newren","fromEmail":"newren@gmail.com","sentAt":"2020-12-20T02:19:50Z","receivedAt":"2020-12-20T02:21:03Z","isPatch":false,"sender":{"key":"newren@gmail.com","avatar":"https://avatars.githubusercontent.com/u/5455730?v=4"},"body":"On Fri, Dec 18, 2020 at 9:37 PM Junio C Hamano <gitster@pobox.com> wrote:\n\n> A release candidate 2.30-rc1 has been tagged; there are too many\n> topics in flight, sadly many of which haven't been adequately\n> reviewed.  I think there are a couple of topics left in 'next' that\n> are obvious candidates for the final, but it would be lovely if we\n> can figure out how to get topics in 'seen' that haven't got enough\n> love unstuck.\n\nI'll try to post an RFC on the sparse-checkout handling soon; sorry\nit's taken me a while.  One question on your labelling for the\nmerge-ort, stuff, though...\n\n> * en/merge-ort-recursive (2020-12-16) 4 commits\n>  - merge-ort: implement merge_incore_recursive()\n>  - merge-ort: make clear_internal_opts() aware of partial clearing\n>  - merge-ort: copy a few small helper functions from merge-recursive.c\n>  - commit: move reverse_commit_list() from merge-recursive\n>  (this branch uses en/merge-ort-2 and en/merge-ort-impl; is tangled with en/merge-ort-3.)\n\n...this comment here is repeated below...\n\n> * en/merge-ort-3 (2020-12-15) 11 commits\n>  - merge-ort: add implementation of type-changed rename handling\n>  - merge-ort: add implementation of normal rename handling\n>  - merge-ort: add implementation of rename collisions\n>  - merge-ort: add implementation of rename/delete conflicts\n>  - merge-ort: add implementation of both sides renaming differently\n>  - merge-ort: add implementation of both sides renaming identically\n>  - merge-ort: add basic outline for process_renames()\n>  - merge-ort: implement compare_pairs() and collect_renames()\n>  - merge-ort: implement detect_regular_renames()\n>  - merge-ort: add initial outline for basic rename detection\n>  - merge-ort: add basic data structures for handling renames\n>  (this branch uses en/merge-ort-2 and en/merge-ort-impl; is tangled with en/merge-ort-recursive.)\n\nWhat do you mean when you say these two topics are tangled?  They were\nwritten to avoid all contextual conflicts, and to be allowed to merge\nin either order, and I just re-verified that they merge cleanly.  So\nI'm not understanding this comment.\n\nIf there are any remaining issues in this series, I'd be happy to fix\nthem up.  I'm not aware of any, and Stollee has reviewed the\nseries[1].  I was planning on submitting another topic next week,\ndirectory rename detection, that builds on this series.\n\n[1] https://lore.kernel.org/git/6448806f-791b-610a-06de-7be5650334e6@gmail.com/,\nnote that his comment was on series v2 and I addressed his one\nremaining point in v3.\n"},{"id":"412677","messageId":"xmqqblepnd9k.fsf@gitster.c.googlers.com","threadId":"54853","inReplyTo":"CABPp-BFoSz40-1mNLrxCgMTccYqLOg6ifX5PeLDutbimF9ysPQ@mail.gmail.com","subject":"Re: What's cooking in git.git (Dec 2020, #03; Fri, 18)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2020-12-20T07:32:39Z","receivedAt":"2020-12-20T07:41:07Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Elijah Newren <newren@gmail.com> writes:\n\n> What do you mean when you say these two topics are tangled?\n\nWhen two topics are \"one builds on top of the whole of the other\",\nmy tool labels \"uses\" vs \"is used by\".  All other cases where two\ntopics share a commit are labeled as \"tangled\", as I couldn't come\nup with any better phrase.\n"},{"id":"412713","messageId":"CAFQ2z_MtpPNSpL9=OoyPfDRfkFxnCO19qBDnY9bnZiEEGtuMsQ@mail.gmail.com","threadId":"54853","inReplyTo":"xmqq7dpeqrz4.fsf@gitster.c.googlers.com","subject":"Re: What's cooking in git.git (Dec 2020, #03; Fri, 18)","fromName":"Han-Wen Nienhuys","fromEmail":"hanwen@google.com","sentAt":"2020-12-21T12:40:03Z","receivedAt":"2020-12-21T12:41:08Z","isPatch":false,"sender":{"key":"hanwen@google.com","avatar":"https://avatars.githubusercontent.com/u/31547?v=4"},"body":"On Sat, Dec 19, 2020 at 6:36 AM Junio C Hamano <gitster@pobox.com> wrote:\n\n> * hn/reftable (2020-12-09) 15 commits\n>  . Add \"test-tool dump-reftable\" command.\n>  . git-prompt: prepare for reftable refs backend\n>  . Reftable support for git-core\n>  . reftable: rest of library\n>  . reftable: reftable file level tests\n>  . reftable: read reftable files\n>  . reftable: write reftable files\n>  . reftable: a generic binary tree implementation\n>  . reftable: reading/writing blocks\n>  . reftable: (de)serialization for the polymorphic record type.\n>  . reftable: add blocksource, an abstraction for random access reads\n>  . reftable: utility functions\n>  . reftable: add error related functionality\n>  . reftable: add LICENSE\n>  . init-db: set the_repository->hash_algo early on\n>\n>  The \"reftable\" backend for the refs API.\n>\n>  Ejected for now, as it has been breaking the tip of 'seen' for too\n>  long.\n\n\nCan you provide more information here? The PR at\nhttps://github.com/git/git/pull/847 passes all tests (except for the\nVSBuild, with errors that seem unrelated.)\n\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":"412717","messageId":"CAPc5daWFn3Y_MYUAPWgmYQEu9-9PYROewczrzGfd4qs8dvaZAw@mail.gmail.com","threadId":"54853","inReplyTo":"CABPp-BErnY+zfmp-LWTe0EUB5QKKcLCP=4t9VxwvA_+DaBvDuw@mail.gmail.com","subject":"Re: What's cooking in git.git (Dec 2020, #03; Fri, 18)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2020-12-21T17:50:27Z","receivedAt":"2020-12-21T17:51:42Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"> I'm still confused.  en/merge-ort-3 and en/merge-ort-recursive do not\n> share any commits.  The only tie is that each \"uses en/merge-ort-2\",\n> as you noted, but that was already noted separately.  Am I missing\n> something?\n\nYes, en/merge-ort-2 is not yet merged to 'master' and these two share\nthe commits on them. Due to lack of better phrase that is labeled as\n\"tangled\".\n"},{"id":"412720","messageId":"xmqqim8vm41g.fsf@gitster.c.googlers.com","threadId":"54853","inReplyTo":"CAFQ2z_MtpPNSpL9=OoyPfDRfkFxnCO19qBDnY9bnZiEEGtuMsQ@mail.gmail.com","subject":"Re: What's cooking in git.git (Dec 2020, #03; Fri, 18)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2020-12-21T18:01:47Z","receivedAt":"2020-12-21T18:02:35Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Han-Wen Nienhuys <hanwen@google.com> writes:\n\n> On Sat, Dec 19, 2020 at 6:36 AM Junio C Hamano <gitster@pobox.com> wrote:\n>\n>> * hn/reftable (2020-12-09) 15 commits\n>>  . Add \"test-tool dump-reftable\" command.\n>>  . git-prompt: prepare for reftable refs backend\n>>  . Reftable support for git-core\n>>  . reftable: rest of library\n>>  . reftable: reftable file level tests\n>>  . reftable: read reftable files\n>>  . reftable: write reftable files\n>>  . reftable: a generic binary tree implementation\n>>  . reftable: reading/writing blocks\n>>  . reftable: (de)serialization for the polymorphic record type.\n>>  . reftable: add blocksource, an abstraction for random access reads\n>>  . reftable: utility functions\n>>  . reftable: add error related functionality\n>>  . reftable: add LICENSE\n>>  . init-db: set the_repository->hash_algo early on\n>>\n>>  The \"reftable\" backend for the refs API.\n>>\n>>  Ejected for now, as it has been breaking the tip of 'seen' for too\n>>  long.\n>\n>\n> Can you provide more information here? The PR at\n> https://github.com/git/git/pull/847 passes all tests (except for the\n> VSBuild, with errors that seem unrelated.)\n\nSorry, but it has been a long time that I have no more detail than\nthe above handy.  Older CI history might know more, but I have no\ntime to dig that right now (and I'd be just as efficient as you\nwould for doing such things).\n\nI can try including it in one of the today's pushout of 'seen' and\nsee what breaks, which would be the easiest ;-)\n\nThanks for pinging.\n"},{"id":"412745","messageId":"CABPp-BErnY+zfmp-LWTe0EUB5QKKcLCP=4t9VxwvA_+DaBvDuw@mail.gmail.com","threadId":"54853","inReplyTo":"xmqqblepnd9k.fsf@gitster.c.googlers.com","subject":"Re: What's cooking in git.git (Dec 2020, #03; Fri, 18)","fromName":"Elijah Newren","fromEmail":"newren@gmail.com","sentAt":"2020-12-21T17:25:15Z","receivedAt":"2020-12-21T18:27:47Z","isPatch":false,"sender":{"key":"newren@gmail.com","avatar":"https://avatars.githubusercontent.com/u/5455730?v=4"},"body":"On Sat, Dec 19, 2020 at 11:32 PM Junio C Hamano <gitster@pobox.com> wrote:\n>\n> Elijah Newren <newren@gmail.com> writes:\n>\n> > What do you mean when you say these two topics are tangled?\n>\n> When two topics are \"one builds on top of the whole of the other\",\n> my tool labels \"uses\" vs \"is used by\".  All other cases where two\n> topics share a commit are labeled as \"tangled\", as I couldn't come\n> up with any better phrase.\n\nI'm still confused.  en/merge-ort-3 and en/merge-ort-recursive do not\nshare any commits.  The only tie is that each \"uses en/merge-ort-2\",\nas you noted, but that was already noted separately.  Am I missing\nsomething?\n"},{"id":"412767","messageId":"xmqqsg7zkk75.fsf_-_@gitster.c.googlers.com","threadId":"54853","inReplyTo":"xmqqim8vm41g.fsf@gitster.c.googlers.com","subject":"[PATCH] SQUASH??? allow t0031 to run with any default branch name","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2020-12-21T19:55:42Z","receivedAt":"2020-12-21T19:56:41Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Junio C Hamano <gitster@pobox.com> writes:\n\n>>>  The \"reftable\" backend for the refs API.\n>>>\n>>>  Ejected for now, as it has been breaking the tip of 'seen' for too\n>>>  long.\n>>\n>>\n>> Can you provide more information here? The PR at\n>> https://github.com/git/git/pull/847 passes all tests (except for the\n>> VSBuild, with errors that seem unrelated.)\n>\n> Sorry, but it has been a long time that I have no more detail than\n> the above handy.  Older CI history might know more, but I have no\n> time to dig that right now (and I'd be just as efficient as you\n> would for doing such things).\n>\n> I can try including it in one of the today's pushout of 'seen' and\n> see what breaks, which would be the easiest ;-)\n>\n> Thanks for pinging.\n\nI just pushed one this morning, the only change from yesterday's\n'seen' is that it has hn/reftable at the tip.\n\n  https://travis-ci.org/github/git/git/jobs/750888904\n\nIt seems that we should stop assuming what the name of the default\nbranch is in a new repository.  One good way to do so would be to\nchange \"git init\" to \"git init -b primary\" so that the tests won't\nget affected whether the default name is master or main or any other\nvalue, and then use 'primary' throughout the name, instead of\nassuming 'master' will stay to be the name used when unspecified\nforever.\n\nI'll queue the following on tip to force the test pass, but please\nsquash it into an appropriate step in the patch series; fixing it in\na different way may also be acceptable and welcome, if you or others\ncan come up with a cleaner way to do so.\n\nThanks.\n\n--- >8 ------ >8 ------ >8 ------ >8 ------ >8 ------ >8 ------ >8 ------ >8 ---\nSubject: [PATCH] SQUASH??? allow t0031 to run with any default branch name\n\nSigned-off-by: Junio C Hamano <gitster@pobox.com>\n---\n t/t0031-reftable.sh | 54 ++++++++++++++++++++++++---------------------\n 1 file changed, 29 insertions(+), 25 deletions(-)\n\ndiff --git a/t/t0031-reftable.sh b/t/t0031-reftable.sh\nindex 58c7d5d4bc..ba0738e515 100755\n--- a/t/t0031-reftable.sh\n+++ b/t/t0031-reftable.sh\n@@ -9,23 +9,27 @@ test_description='reftable basics'\n \n INVALID_SHA1=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\n \n+git_init () {\n+\tgit init -b primary \"$@\"\n+}\n+\n initialize ()  {\n \trm -rf .git &&\n-\tgit init --ref-storage=reftable &&\n+\tgit_init --ref-storage=reftable &&\n \tmv .git/hooks .git/hooks-disabled\n }\n \n test_expect_success 'SHA256 support, env' '\n \trm -rf .git &&\n \tGIT_DEFAULT_HASH=sha256 && export GIT_DEFAULT_HASH &&\n-\tgit init --ref-storage=reftable &&\n+\tgit_init --ref-storage=reftable &&\n \tmv .git/hooks .git/hooks-disabled &&\n \ttest_commit file\n '\n \n test_expect_success 'SHA256 support, option' '\n \trm -rf .git &&\n-\tgit init --ref-storage=reftable --object-format=sha256 &&\n+\tgit_init --ref-storage=reftable --object-format=sha256 &&\n \tmv .git/hooks .git/hooks-disabled &&\n \ttest_commit file\n '\n@@ -34,13 +38,13 @@ test_expect_success 'delete ref' '\n \tinitialize &&\n \ttest_commit file &&\n \tSHA=$(git show-ref -s --verify HEAD) &&\n-\ttest_write_lines \"$SHA refs/heads/master\" \"$SHA refs/tags/file\" >expect &&\n-\tgit show-ref > actual &&\n+\ttest_write_lines \"$SHA refs/heads/primary\" \"$SHA refs/tags/file\" >expect &&\n+\tgit show-ref >actual &&\n \t! git update-ref -d refs/tags/file $INVALID_SHA1 &&\n \ttest_cmp expect actual &&\n \tgit update-ref -d refs/tags/file $SHA  &&\n-\ttest_write_lines \"$SHA refs/heads/master\" >expect &&\n-\tgit show-ref > actual &&\n+\ttest_write_lines \"$SHA refs/heads/primary\" >expect &&\n+\tgit show-ref >actual &&\n \ttest_cmp expect actual\n '\n \n@@ -54,9 +58,9 @@ test_expect_success 'clone calls transaction_initial_commit' '\n test_expect_success 'basic operation of reftable storage: commit, show-ref' '\n \tinitialize &&\n \ttest_commit file &&\n-\ttest_write_lines refs/heads/master refs/tags/file >expect &&\n+\ttest_write_lines refs/heads/primary refs/tags/file >expect &&\n \tgit show-ref &&\n-\tgit show-ref | cut -f2 -d\" \" > actual &&\n+\tgit show-ref | cut -f2 -d\" \" >actual &&\n \ttest_cmp actual expect\n '\n \n@@ -70,12 +74,12 @@ test_expect_success 'reflog, repack' '\n \tgit pack-refs &&\n \tls -1 .git/reftable >table-files &&\n \ttest_line_count = 2 table-files &&\n-\tgit reflog refs/heads/master >output &&\n+\tgit reflog refs/heads/primary >output &&\n \ttest_line_count = 10 output &&\n \tgrep \"commit (initial): number 1\" output &&\n \tgrep \"commit: number 10\" output &&\n \tgit gc &&\n-\tgit reflog refs/heads/master >output &&\n+\tgit reflog refs/heads/primary >output &&\n \ttest_line_count = 0 output\n '\n \n@@ -86,8 +90,8 @@ test_expect_success 'branch switch in reflog output' '\n \ttest_commit file2 &&\n \tgit checkout -b branch2 &&\n \tgit switch - &&\n-\tgit rev-parse --symbolic-full-name HEAD > actual &&\n-\techo refs/heads/branch1 > expect &&\n+\tgit rev-parse --symbolic-full-name HEAD >actual &&\n+\techo refs/heads/branch1 >expect &&\n \ttest_cmp actual expect\n '\n \n@@ -102,7 +106,7 @@ test_expect_success 'peeled tags are stored' '\n \ttest_commit file &&\n \tgit tag -m \"annotated tag\" test_tag HEAD &&\n \t{\n-\t\tprint_ref \"refs/heads/master\" &&\n+\t\tprint_ref \"refs/heads/primary\" &&\n \t\tprint_ref \"refs/tags/file\" &&\n \t\tprint_ref \"refs/tags/test_tag\" &&\n \t\tprint_ref \"refs/tags/test_tag^{}\"\n@@ -114,32 +118,32 @@ test_expect_success 'peeled tags are stored' '\n test_expect_success 'show-ref works on fresh repo' '\n \tinitialize &&\n \trm -rf .git &&\n-\tgit init --ref-storage=reftable &&\n+\tgit_init --ref-storage=reftable &&\n \t>expect &&\n-\t! git show-ref > actual &&\n+\t! git show-ref >actual &&\n \ttest_cmp expect actual\n '\n \n test_expect_success 'checkout unborn branch' '\n \tinitialize &&\n-\tgit checkout -b master\n+\tgit checkout -b primary\n '\n \n \n test_expect_success 'dir/file conflict' '\n \tinitialize &&\n \ttest_commit file &&\n-\t! git branch master/forbidden\n+\t! git branch primary/forbidden\n '\n \n \n test_expect_success 'do not clobber existing repo' '\n \trm -rf .git &&\n-\tgit init --ref-storage=files &&\n-\tcat .git/HEAD > expect &&\n+\tgit_init --ref-storage=files &&\n+\tcat .git/HEAD >expect &&\n \ttest_commit file &&\n-\t(git init --ref-storage=reftable || true) &&\n-\tcat .git/HEAD > actual &&\n+\t(git_init --ref-storage=reftable || true) &&\n+\tcat .git/HEAD >actual &&\n \ttest_cmp expect actual\n '\n \n@@ -168,7 +172,7 @@ test_expect_success 'rebase' '\n '\n \n test_expect_success 'worktrees' '\n-\tgit init --ref-storage=reftable start &&\n+\tgit_init --ref-storage=reftable start &&\n \t(cd start && test_commit file1 && git checkout -b branch1 &&\n \tgit checkout -b branch2 &&\n \tgit worktree add  ../wt\n@@ -182,13 +186,13 @@ test_expect_success 'worktrees 2' '\n \tinitialize &&\n \ttest_commit file1 &&\n \tmkdir existing_empty &&\n-\tgit worktree add --detach existing_empty master\n+\tgit worktree add --detach existing_empty primary\n '\n \n test_expect_success 'FETCH_HEAD' '\n \tinitialize &&\n \ttest_commit one &&\n-\t(git init sub && cd sub && test_commit two) &&\n+\t(git_init sub && cd sub && test_commit two) &&\n \tgit --git-dir sub/.git rev-parse HEAD >expect &&\n \tgit fetch sub &&\n \tgit checkout FETCH_HEAD &&\n-- \n2.30.0-rc1-180-g539a9eda38\n\n"},{"id":"412771","messageId":"5fe1036d63729_f938208b3@natae.notmuch","threadId":"54853","inReplyTo":"xmqqsg7zkk75.fsf_-_@gitster.c.googlers.com","subject":"RE: [PATCH] SQUASH??? allow t0031 to run with any default branch name","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2020-12-21T20:19:57Z","receivedAt":"2020-12-21T20:20:42Z","isPatch":true,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Junio C Hamano wrote:\n> It seems that we should stop assuming what the name of the default\n> branch is in a new repository.  One good way to do so would be to\n> change \"git init\" to \"git init -b primary\" so that the tests won't\n> get affected whether the default name is master or main or any other\n> value, and then use 'primary' throughout the name, instead of\n> assuming 'master' will stay to be the name used when unspecified\n> forever.\n\nA better name would be \"initial\".\n\nEven in tests branch names should mean something, and in the context of\ngit, the master branch means the original branch from which all the\nother branches were copied from (usually). In tests the primary branch\nis not necessarily the master branch, so \"primary\" doesn't cut it.\n\nAnother option is \"original\".\n\nIf the meaning of the word is not defined yet, a placeholder can be \"nonce\".\n\nOr if we don't want to assign any meaning at all, just \"blank\", \"nil\",\nand of course \"foobar\".\n\nCheers.\n\n-- \nFelipe Contreras\n"},{"id":"412847","messageId":"CAFQ2z_PuPcpuX6OQ3r7yYuOwaGEiT0xNaCnVNq4xE-mW-5sezA@mail.gmail.com","threadId":"54853","inReplyTo":"xmqqsg7zkk75.fsf_-_@gitster.c.googlers.com","subject":"Re: [PATCH] SQUASH??? allow t0031 to run with any default branch name","fromName":"Han-Wen Nienhuys","fromEmail":"hanwen@google.com","sentAt":"2020-12-22T10:22:32Z","receivedAt":"2020-12-22T10:23:41Z","isPatch":true,"sender":{"key":"hanwen@google.com","avatar":"https://avatars.githubusercontent.com/u/31547?v=4"},"body":"On Mon, Dec 21, 2020 at 8:55 PM Junio C Hamano <gitster@pobox.com> wrote:\n> I'll queue the following on tip to force the test pass, but please\n> squash it into an appropriate step in the patch series; fixing it in\n> a different way may also be acceptable and welcome, if you or others\n> can come up with a cleaner way to do so.\n\nthanks, I've folded this patch in.\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"}]}