From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id ACBFA1F953 for ; Sat, 4 Dec 2021 01:37:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1384028AbhLDBk4 (ORCPT ); Fri, 3 Dec 2021 20:40:56 -0500 Received: from pb-smtp21.pobox.com ([173.228.157.53]:54150 "EHLO pb-smtp21.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1354316AbhLDBkz (ORCPT ); Fri, 3 Dec 2021 20:40:55 -0500 Received: from pb-smtp21.pobox.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 7C424166F61; Fri, 3 Dec 2021 20:37:30 -0500 (EST) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=from:to :subject:date:message-id:mime-version:content-type :content-transfer-encoding; s=sasl; bh=zxfiaj7AS6P1NZJ6O5o8aAlMY JfRXyWUo5m89EFjt8k=; b=WL+u+oLh4WNuM8EP1J+hBh3EElzspVKXJfGeuH56b 1DRn35+gB7a0JJnp+yHyHUSpzQPQdJrWSYI/QdmOyB62nyBGbJ/ZQZGnH7QnsyHQ bvUtR8I5UxJ/ZM22Z8qKwO2Y4gsMcNc1ULDVm0uEj+dqdDUul8uhxEB3lfncMS7s MY= Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 74DEC166F60; Fri, 3 Dec 2021 20:37:30 -0500 (EST) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [104.133.2.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp21.pobox.com (Postfix) with ESMTPSA id 6ECE6166F5D; Fri, 3 Dec 2021 20:37:26 -0500 (EST) (envelope-from junio@pobox.com) From: Junio C Hamano To: git@vger.kernel.org Subject: What's cooking in git.git (Dec 2021, #01; Fri, 3) X-master-at: abe6bb3905392d5eb6b01fa6e54d7e784e0522aa X-next-at: a8338297339b1ab064e799c15c4fc56c122ef967 Date: Fri, 03 Dec 2021 17:37:23 -0800 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Pobox-Relay-ID: BC722FB2-54A2-11EC-BD95-98D80D944F46-77302942!pb-smtp21.pobox.com Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org This is probably the first issue of the "What's cooking" report, in which all topics have some sort of description. That's a small achievement, at least for me. Even better, each and every topic is annotated with some sort of verdict (like "Will discard", "Expecting a reroll", "Will merge to 'next'?" etc.). There is no topic in the "Undecided" category when this report is fed to "cook -w" script (found in the 'todo' branch). A handful of topics are added to 'next', and we have about 40 topics cooking there. For them, the future is automated---they spend about a week in 'next', and if we find issues in them, we incrementally improve them, or get merged to 'master'. Then we have about a dozen topics that are marked for 'next' (please raise your hand if you have objection before a real damage is done), and 8 more that may be ready for 'next' (please raise your hand if you want to nudge them in either direction, for or against). Here are the topics that have been cooking in my tree. Commits prefixed with '+' are in 'next' (being in 'next' is a sign that a topic is stable enough to be used and are candidate to be in a future release). Commits prefixed with '-' are only in 'seen', which means nothing more than that I have found them of interest for some reason (like "it may have hard-to-resolve conflicts with another topic already in flight" or "this may turn out to be useful"). Do not read too much into a topic being in (or not in) 'seen'. The ones marked with '.' do not appear in any of the integration branches, but I am still holding onto them. A few topics for regression fixes have been merged to 'next' and will be merged to 'master' shortly. There are many topics listed as "New" that are in 'seen', but I haven't read many of them (and I shouldn't have anyway, before dealing with regression fixes) and haven't gave any summary comments in this report, either, yet. Copies of the source code to Git live in many repositories, and the following is a list of the ones I push into or their mirrors. Some repositories have only a subset of branches. With maint, master, next, seen, todo: git://git.kernel.org/pub/scm/git/git.git/ git://repo.or.cz/alt-git.git/ https://kernel.googlesource.com/pub/scm/git/git/ https://github.com/git/git/ https://gitlab.com/git-vcs/git/ With all the integration branches and topics broken out: https://github.com/gitster/git/ Even though the preformatted documentation in HTML and man format are not sources, they are published in these repositories for convenience (replace "htmldocs" with "manpages" for the manual pages): git://git.kernel.org/pub/scm/git/git-htmldocs.git/ https://github.com/gitster/git-htmldocs.git/ Release tarballs are available at: https://www.kernel.org/pub/software/scm/git/ -------------------------------------------------- [New Topics] * ab/cat-file (2021-11-29) 10 commits - cat-file: use GET_OID_ONLY_TO_DIE in --(textconv|filters) - object-name.c: don't have GET_OID_ONLY_TO_DIE imply *_QUIETLY - cat-file: correct and improve usage information - cat-file: fix remaining usage bugs - cat-file: make --batch-all-objects a CMDMODE - cat-file: move "usage" variable to cmd_cat_file() - cat-file docs: fix SYNOPSIS and "-h" output - parse-options API: add a usage_msg_optf() - cat-file tests: test messaging on bad objects/paths - cat-file tests: test bad usage Assorted updates to "git cat-file", especially "-h". Needs review. Even though this is at its third round, there wasn't any meaningful reviews other than typofixes in the earliest round, which may or may not be still relevant. The last round needs a serious review before becoming eligible for 'next'. source: * ab/grep-patterntype (2021-11-29) 7 commits - grep: simplify config parsing and option parsing - grep API: call grep_config() after grep_init() - grep.c: don't pass along NULL callback value - built-ins: trust the "prefix" from run_builtin() - grep tests: add missing "grep.patternType" config test - log tests: check if grep_config() is called by "log"-like cmds - grep.h: remove unused "regex_t regexp" from grep_opt Some code clean-up in the "git grep" machinery. Need to pick up a reroll. cf. source: * en/rebase-x-fix (2021-11-29) 1 commit (merged to 'next' on 2021-12-03 at a833829733) + sequencer: avoid adding exec commands for non-commit creating commands "git rebase -x" added an unnecessary 'exec' instructions before 'noop', which has been corrected. Will merge to 'master'. source: * js/use-builtin-add-i (2021-12-01) 2 commits - add -i: default to the built-in implementation - t2016: require the PERL prereq only when necessary "git add -i" was rewritten in C some time ago and has been in testing; the reimplementation is now exposed to general public by default. On hold. There are known breakages on macOS. cf. source: * jt/conditional-config-on-remote-url (2021-11-29) 2 commits - config: include file if remote URL matches a glob - config: make git_config_include() static The conditional inclusion mechanism of configuration files using "[includeIf ]" learns to base its decision on the URL of the remote repository the repository interacts with. Need to pick up a reroll. cf. source: <3b3af0da983c65ac8282b14141495f6859cd575a.1638217387.git.jonatha= ntanmy@google.com> * tb/cruft-packs (2021-11-29) 17 commits - sha1-file.c: don't freshen cruft packs - builtin/gc.c: conditionally avoid pruning objects via loose - builtin/repack.c: add cruft packs to MIDX during geometric repack - builtin/repack.c: use named flags for existing_packs - builtin/repack.c: allow configuring cruft pack generation - builtin/repack.c: support generating a cruft pack - builtin/pack-objects.c: --cruft with expiration - reachable: report precise timestamps from objects in cruft packs - reachable: add options to add_unseen_recent_objects_to_traversal - builtin/pack-objects.c: --cruft without expiration - builtin/pack-objects.c: return from create_object_entry() - t/helper: add 'pack-mtimes' test-tool - pack-mtimes: support writing pack .mtimes files - chunk-format.h: extract oid_version() - pack-write: pass 'struct packing_data' to 'stage_tmp_packfiles' - pack-mtimes: support reading .mtimes files - Documentation/technical: add cruft-packs.txt Instead of leaving unreachable objects in loose form when packing, or ejecting them into loose form when repacking, gather them in a packfile with an auxiliary file that records the last-use time of these objects. Expecting a reroll. source: * cb/save-term-across-editor-invocation (2021-12-01) 3 commits - fixup! editor: allow for saving/restoring terminal state - editor: allow for saving/restoring terminal state - terminal: teach save_term to fail when not foreground Some editors are reported to leave the terminal in funny state after they exit on Windows. Work it around by saving and restoring the terminal state when needed. Expecting a reroll. cf. source: <20211202035446.1154-1-carenas@gmail.com> * jk/log-decorate-opts-with-implicit-decorate (2021-12-01) 2 commits - log: load decorations with --simplify-by-decoration - log: handle --decorate-refs with userformat "%d" When "git log" implicitly enabled the "decoration" processing without being explicitly asked with "--decorate" option, it failed to read and honor the settings given by the "--decorate-refs" option. Will merge to 'next'? source: * jl/subtree-check-parents-argument-passing-fix (2021-12-01) 1 commit - subtree: fix argument handling in check_parents Fix performance-releated bug in "git subtree" (in contrib/). Expecting a reroll. cf. source: -------------------------------------------------- [Stalled] * ar/submodule-update (2021-10-13) 9 commits . submodule--helper: rename helper functions . submodule--helper: remove unused helpers . submodule: move core cmd_update() logic to C . submodule--helper: run update using child process struct . submodule--helper: allow setting superprefix for init_submodule() . submodule--helper: refactor get_submodule_displaypath() . submodule--helper: rename helpers for update-clone . submodule--helper: get remote names from any repository . submodule--helper: split up ensure_core_worktree() Rewrite of "git submodule update" in C. Expecting a reroll? cf. source: <20211013051805.45662-10-raykar.ath@gmail.com> * cf/fetch-set-upstream-while-detached (2021-07-06) 1 commit - fetch: fix segfault on --set-upstream while on a detached HEAD "git fetch --set-upstream" while on detached HEAD segfaulted instead of noticing that such an operation did not make sense. Expecting a reroll. A low hanging fruit to make this usable is an addition of a few tests; any takers? cf. cf. source: <20210706162238.575988-1-clemens@endorphin.org> * ms/customizable-ident-expansion (2021-09-01) 1 commit - keyword expansion: make "$Id$" string configurable Instead of "$Id$", user-specified string (like $FreeBSD$) can be used as an in-blob placeholder for keyword expansion. Will discard. Stalled for too long. cf. cf. <211101.86fssf3bn3.gmgdl@evledraar.gmail.com> source: * pw/fix-some-issues-in-reset-head (2021-10-01) 12 commits - rebase -m: don't fork git checkout - rebase --apply: set ORIG_HEAD correctly - rebase --apply: fix reflog - reset_head(): take struct rebase_head_opts - rebase: cleanup reset_head() calls - reset_head(): make default_reflog_action optional - reset_head(): factor out ref updates - reset_head(): remove action parameter - reset_head(): don't run checkout hook if there is an error - reset_head(): fix checkout - rebase: factor out checkout for up to date branch - Merge branch 'pw/rebase-of-a-tag-fix' into pw/fix-some-issues-in-reset= -head Fix "some issues" in a helper function reset_head(). Will discard. This needs a lot better explanation, including what the issues are, which codepaths the helper is used in and to do what, and tests to protect the fixes. source: -------------------------------------------------- [Cooking] * ab/ambiguous-object-name (2021-11-26) 6 commits - object-name: re-use "struct strbuf" in show_ambiguous_object() - object-name: iterate ambiguous objects before showing header - object-name: show date for ambiguous tag objects - object-name: make ambiguous object output translatable - object-name: explicitly handle OBJ_BAD in show_ambiguous_object() - object-name tests: add tests for ambiguous object blind spots Error output given in response to an ambiguous object name has been improved. Needs review. An earlier iteration that was much smaller had seen some reviews, but the latest round enlarged its scope and needs to be reviewed afresh. source: * cb/add-p-single-key-fix (2021-11-28) 1 commit (merged to 'next' on 2021-12-03 at 8d4f16e620) + add -p: avoid use of undefined $key when ReadKey -> EOF The single-key-input mode in "git add -p" had some code to handle keys that generate a sequence of input via ReadKey(), which did not handle end-of-file correctly, which has been fixed. Will merge to 'master'. source: <20211128174903.5623-1-carenas@gmail.com> * cb/mingw-gmtime-r (2021-11-27) 1 commit (merged to 'next' on 2021-12-03 at 785278d40e) + mingw: avoid fallback for {local,gm}time_r() Build fix on Windows. Will merge to 'master'. source: * ds/trace2-regions-in-tests (2021-11-29) 2 commits - t/t*: remove custom GIT_TRACE2_EVENT_NESTING - test-lib.sh: set GIT_TRACE2_EVENT_NESTING The default setting for trace2 event nesting was too low to cause test failures, which is worked around by bumping it up in the test framework. Will merge to 'next'. source: * hn/allow-bogus-oid-in-ref-tests (2021-12-02) 8 commits - t1430: create valid symrefs using test-helper - t1430: remove refs using test-tool - refs: introduce REF_SKIP_REFNAME_VERIFICATION flag - refs: introduce REF_SKIP_OID_VERIFICATION flag - refs: update comment. - test-ref-store: plug memory leak in cmd_delete_refs - test-ref-store: parse symbolic flag constants - test-ref-store: remove force-create argument for create-reflog The test helper for refs subsystem learned to write bogus and/or nonexistent object name to refs to simulate error situations we want to test Git in. Will merge to 'next'. source: * hn/t1404-df-limitation-is-ref-files-only (2021-11-29) 1 commit - t1404: mark directory/file conflict tests with REFFILES Test update. Will merge to 'next'. source: * jc/reflog-iterator-callback-doc (2021-11-28) 1 commit - refs: document callback for reflog-ent iterators Document the parameters given to the reflog entry iterator callback functions. Will merge to 'next'? source: * po/size-t-for-vs (2021-12-01) 3 commits (merged to 'next' on 2021-12-02 at 489c5b0046) + object-file.c: LLP64 compatibility, upcast unity for left shift + diffcore-delta.c: LLP64 compatibility, upcast unity for left shift + repack.c: LLP64 compatibility, upcast unity for left shift On platforms where ulong is shorter than size_t, code paths that shifted 1 or 1U to the left lacked the necessary cast to size_t, which have been corrected. Will merge to 'master'. source: <20211201002902.1042-4-philipoakley@iee.email> * yn/complete-date-format-options (2021-11-25) 1 commit (merged to 'next' on 2021-12-03 at 4f37a904a1) + completion: add human and auto: date format The completion script (in contrib/) learns that the "--date" option of commands from the "git log" family takes "human" and "auto" as valid values. Will merge to 'master'. source: * jc/grep-patterntype-default-doc (2021-11-29) 1 commit - grep: clarify what `grep.patternType=3Ddefault` means Doc update. Will merge to 'next'. source: * ab/ci-updates (2021-11-23) 5 commits - CI: don't run "make test" twice in one job - CI: use "$runs_on_pool", not "$jobname" to select packages & config - CI: rename the "Linux32" job to lower-case "linux32" - CI: use shorter names that fit in UX tooltips - CI: remove Travis CI support Drop support for TravisCI and update test workflows at GitHub. Will merge to 'next'. source: * en/keep-cwd (2021-12-01) 11 commits - t2501: simplify the tests since we can now assume desired behavior - dir: new flag to remove_dir_recurse() to spare the original_cwd - dir: avoid incidentally removing the original_cwd in remove_path() - stash: do not attempt to remove startup_info->original_cwd - rebase: do not attempt to remove startup_info->original_cwd - clean: do not attempt to remove startup_info->original_cwd - symlinks: do not include startup_info->original_cwd in dir removal - unpack-trees: add special cwd handling - unpack-trees: refuse to remove startup_info->original_cwd - setup: introduce startup_info->original_cwd - t2501: add various tests for removing the current working directory Many git commands that deal with working tree files try to remove a directory that becomes empty (i.e. "git switch" from a branch that has the directory to another branch that does not would attempt remove all files in the directory and the directory itself). This drops users into an unfamiliar situation if the command was run in a subdirectory that becomes subject to removal due to the command. The commands have been taught to keep an empty directory if it is the directory they were started in to avoid surprising users. Needs review. There are some comments on earlier rounds; the latest one needs a serious review or at least Acks from past commentors. source: * ab/run-command (2021-11-25) 9 commits - run-command API: remove "env" member, always use "env_array" - difftool: use "env_array" to simplify memory management - run-command API: remove "argv" member, always use "args" - run-command API users: use strvec_push(), not argv construction - run-command API users: use strvec_pushl(), not argv construction - run-command tests: use strvec_pushv(), not argv assignment - run-command API users: use strvec_pushv(), not argv assignment - upload-archive: use regular "struct child_process" pattern - worktree: stop being overly intimate with run_command() internals API clean-up. Will merge to 'next'. cf. <211130.86k0gpcpy2.gmgdl@evledraar.gmail.com> cf. source: * hn/create-reflog-simplify (2021-11-22) 1 commit (merged to 'next' on 2021-12-02 at 87ff49b776) + refs: drop force_create argument of create_reflog API A small simplification of API. Will merge to 'master'. source: * hn/reflog-tests (2021-12-02) 5 commits - refs/debug: trim trailing LF from reflog message - test-ref-store: tweaks to for-each-reflog-ent format - t1405: check for_each_reflog_ent_reverse() more thoroughly - test-ref-store: don't add newline to reflog message - show-branch: show reflog message Prepare tests on ref API to help testing reftable backends. Will merge to 'next'. source: * jt/midx-doc-fix (2021-11-22) 1 commit (merged to 'next' on 2021-12-02 at eac9f263ae) + Doc: no midx and partial clone relation Docfix. Will merge to 'master'. source: <20211122184114.3328662-1-jonathantanmy@google.com> * tl/ls-tree-oid-only (2021-11-22) 1 commit - ls-tree.c: support `--oid-only` option for "git-ls-tree" "git ls-tree" learns "--oid-only" option, similar to "--name-only". Expecting a reroll. source: <6c15b4c176b7c03072fa59a4efd9f6fea7d62eae.1637567328.git.dyronet= eng@gmail.com> * jk/t7006-sigpipe-tests-fix (2021-11-22) 3 commits (merged to 'next' on 2021-12-02 at eefd61931f) + t7006: simplify exit-code checks for sigpipe tests + t7006: clean up SIGPIPE handling in trace2 tests + run-command: unify signal and regular logic for wait_or_whine() The function to cull a child process and determine the exit status had two separate code paths for normal callers and callers in a signal handler, and the latter did not yield correct value when the child has caught a signal. The handling of the exit status has been unified for these two code paths. An existing test with flakiness has also been corrected. Will merge to 'master'. source: * em/missing-pager (2021-11-24) 1 commit (merged to 'next' on 2021-12-03 at 22ad721b52) + pager: fix crash when pager program doesn't exist When a non-existent program is given as the pager, we tried to reuse an uninitialized child_process structure and crashed, which has been fixed. Will merge to 'master'. source: <20211125000239.2336-1-ematsumiya@suse.de> * ab/checkout-branch-info-leakfix (2021-11-18) 1 commit (merged to 'next' on 2021-12-02 at 5922388782) + checkout: fix "branch info" memory leaks Leakfix. Will merge to 'master'. source: * ab/make-dependency (2021-11-18) 24 commits - Makefile: move ".SUFFIXES" rule to shared.mak - Makefile: define $(LIB_H) in terms of $(FIND_SOURCE_FILES) - Makefile: disable GNU make built-in wildcard rules - Makefile: use $(file) I/O instead of "FORCE" when possible - Makefile: correct the dependency graph of hook-list.h - Makefiles: add and use wildcard "mkdir -p" template - Makefile: use $(wspfx) for $(QUIET...) in shared.mak - Makefile: add "$(QUIET)" boilerplate to shared.mak - Makefile: add a "TRACK_template" for GIT-*{FLAGS,DEFINES,...} - Makefile: re-add and use the "shellquote" macros - Makefile: move $(comma), $(empty) and $(space) to shared.mak - Makefiles: add "shared.mak", move ".DELETE_ON_ERROR" to it - Makefile: stop needing @@GIT_VERSION@@ in *.perl scripts - Makefile: create a GIT-PYTHON-DEFINES, like "PERL" - Makefile: correct "GIT-PERL-{DEFINES,HEADER}" dependency graph - Makefile: adjust Perl-related comments & whitespace - Makefile: change "ifndef NO_PERL" to "ifdef NO_PERL" - Makefile: guard Perl-only variable assignments - Makefile: remove "mv $@ $@+" dance redundant to .DELETE_ON_ERROR - Makefile: clean perl/build/ even with NO_PERL=3DY - Makefile: use "=3D" not ":=3D" for po/* and perl/* - Makefile: don't set up "perl/build" rules under NO_PERL=3DY - Makefile: don't invoke msgfmt with --statistics - Merge branch 'ab/sh-retire-helper-functions' into ab/make-dependency Dependency clean-up. Needs review. There are some comments on earlier rounds; the latest one needs a serious review or at least Acks from past commentors. source: * ah/advice-pull-has-no-preference-between-rebase-and-merge (2021-11-19) = 1 commit (merged to 'next' on 2021-12-02 at 1b49913760) + pull: don't say that merge is "the default strategy" The advice message given by "git pull" when the user hasn't made a choice between merge and rebase still said that the merge is the default, which no longer is the case. This has been corrected. Will merge to 'master'. source: <20211118154317.639118-1-alexhenrie24@gmail.com> * ds/fetch-pull-with-sparse-index (2021-11-29) 3 commits - ls-files: add --sparse option - fetch/pull: use the sparse index - Merge branch 'ld/sparse-diff-blame' into ds/fetch-pull-with-sparse-ind= ex (this branch uses ld/sparse-diff-blame and vd/sparse-reset.) "git fetch" and "git pull" are now declared sparse-index clean. Also "git ls-files" learns the "--sparse" option to help debugging. Expecting a reroll? Discussion seems to have stalled, with a few loose ends questions. source: * fs/ssh-signing-other-keytypes (2021-11-19) 2 commits - ssh signing: make sign/amend test more resilient - ssh signing: support non ssh-* keytypes The cryptographic signing using ssh keys can specify literal keys for keytypes whose name do not begin with the "ssh-" prefix by using the "key::" prefix mechanism (e.g. "key::ecdsa-sha2-nistp256"). Will merge to 'next'? source: <20211119150707.3924636-1-fs@gigacodes.de> * fs/test-prereq (2021-12-01) 3 commits - test-lib: make BAIL_OUT() work in tests and prereq - test-lib: introduce required prereq for test runs - test-lib: show missing prereq summary The test framework learns to list unsatisfied test prerequisites, and optionally error out when prerequisites that are expected to be satisfied are not. Will merge to 'next'. source: <20211201085315.576865-1-fs@gigacodes.de> * jk/t5319-midx-corruption-test-deflake (2021-11-18) 1 commit (merged to 'next' on 2021-12-02 at 0ac4fd64aa) + t5319: corrupt more bytes of the midx checksum Test fix. Will merge to 'master'. source: * js/trace2-avoid-recursive-errors (2021-11-18) 1 commit (merged to 'next' on 2021-12-02 at c5b1e5ddec) + trace2: disable tr2_dst before warning on write errors trace2 error code path fix. Will merge to 'master'. source: <5a9e49e7f1540d762374382e1769edf112cf093f.1637272706.git.steadmo= n@google.com> * pw/xdiff-classify-record-in-histogram (2021-11-18) 3 commits (merged to 'next' on 2021-12-02 at 5ccd12d09b) + xdiff: simplify comparison + xdiff: avoid unnecessary memory allocations + diff histogram: intern strings "diff --histogram" optimization. Will merge to 'master'. source: * rs/mergesort (2021-11-18) 1 commit (merged to 'next' on 2021-12-02 at 0490b0ffbd) + mergesort: avoid left shift overflow Bitop fix for platforms whose "long" is 32-bit. Will merge to 'master'. source: <5eabbe1c-4c0f-559a-da21-423afec89e7e@web.de> * xw/am-empty (2021-12-01) 3 commits - am: support --allow-empty to record specific empty patches - am: support --empty=3D