From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 984EAECAAD3 for ; Fri, 9 Sep 2022 23:06:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231128AbiIIXGe (ORCPT ); Fri, 9 Sep 2022 19:06:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48172 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230358AbiIIXGb (ORCPT ); Fri, 9 Sep 2022 19:06:31 -0400 Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 920F491D36 for ; Fri, 9 Sep 2022 16:06:29 -0700 (PDT) Received: by mail-pj1-x1034.google.com with SMTP id q3so2793601pjg.3 for ; Fri, 09 Sep 2022 16:06:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:user-agent:message-id:date:subject:to:from:sender:from :to:cc:subject:date; bh=hWI00rsbfzTmg8CPsx9ppRMx5UQH4XVPQSjCU7zmDWI=; b=Atg5T5HaopttFxl+U0QGm8XiOJcU5rPqY9nNqeUHTcffXC1+km5zE3jNk1HVldvM8F pJKn98w6EBXLMIc/D+x+FB3mD7jiCl2C9JmVuBxpCu6GDdLhcNTJ5PrIgGNlc6HqYtey HnginaeKEWWCHaov3XG5Mubb/zexKfEJWVe7vY3PEQ4d9kFv68/qwWqmgja26qm01+fz SO1adP+PRwWNihnX7KwCKjmICQQ2gFaEugKcyzMUmNZVV3t/jKv58bkDX5ZWdO1kXHlv C1HNesbh3To8N/MY/dmyXXZcsEOrH3U2UNNzUadtoMvObVOnIoIf7g59GYK7wXos7g+O 3OIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:user-agent:message-id:date:subject:to:from:sender :x-gm-message-state:from:to:cc:subject:date; bh=hWI00rsbfzTmg8CPsx9ppRMx5UQH4XVPQSjCU7zmDWI=; b=WBFCKz1/8k9fMwFzTTceNnYpcSwmBH+NgKDAzR7bIsSZG9GZdh4FhGHlDO8FIphQqh OsCKc/p+zquSVuwVSyWI/jPf2BDcZBHjtdcVUfM7I8ws/16LIYMK54+dxroU3FKWoAP9 hyIcDUYXoLNET050ZYsg6vjK4vJM2cfybQgO2jW44hEPQllWMeQgcR4OhAJ57zIcI9tn Yo97kQJkLRAxafUVN0HNi6v3cFvcxXNyDuysBkKNwAfHpWKJ9FuhP0W6u6SF1IA1Hr94 EVEJSGUsw8S3OrS+BPJZssOg0FvZ0Z480lxDQqr5QpZk90M9HiI0yL4jxs5ZodcS8BRg SdNg== X-Gm-Message-State: ACgBeo2/Ky1OMWXZxh9K4b65SI96tWexREq3ocpEBjccKkaLvtRP/EFE 3qvBxpqrCiqBEOiEAhyW0vbpex9YuuY= X-Google-Smtp-Source: AA6agR5rDXOn/nlQYdbRegiJII95qMeOJvMJBQVdiSzEYtl/qsXgplachCYYLpAhm/HpIQ94WFLkqg== X-Received: by 2002:a17:902:f0d4:b0:176:988a:77fd with SMTP id v20-20020a170902f0d400b00176988a77fdmr15670647pla.25.1662764788225; Fri, 09 Sep 2022 16:06:28 -0700 (PDT) Received: from localhost (33.5.83.34.bc.googleusercontent.com. [34.83.5.33]) by smtp.gmail.com with ESMTPSA id u3-20020a17090341c300b00177f82f0789sm968470ple.198.2022.09.09.16.06.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 09 Sep 2022 16:06:27 -0700 (PDT) Sender: Junio C Hamano From: Junio C Hamano To: git@vger.kernel.org Subject: What's cooking in git.git (Sep 2022, #02; Fri, 9) X-master-at: dd3f6c4cae7e3b15ce984dce8593ff7569650e24 X-next-at: 50f0e44ec40b5fab5d618dd26ebd776c47e9af13 Date: Fri, 09 Sep 2022 16:06:27 -0700 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org 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', and aren't considered "accepted" at all. A topic without enough support may be discarded after a long period of no activity. We are at the end of week #9 in a 12-week cycle toward Git 2.38 (tinyurl.com/gitCal). I plan to tag -rc0 (i.e. preview) on the 15th or so, but I expect that many folks are busy in Chicago for Git Merge so let's not make a big fuss about it and instead treat it as just one of the regular updates to the 'master' branch. 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/ -------------------------------------------------- [Graduated to 'master'] * ab/retire-ppc-sha1 (2022-08-31) 2 commits (merged to 'next' on 2022-09-05 at 480da6ef06) + Makefile: use $(OBJECTS) instead of $(C_OBJ) + Makefile + hash.h: remove PPC_SHA1 implementation Remove the assembly version of SHA-1 implementation for PPC. source: * cc/doc-trailer-whitespace-rules (2022-08-30) 1 commit (merged to 'next' on 2022-09-05 at 4c018a3ab7) + Documentation: clarify whitespace rules for trailers Doc update. source: <20220830105046.324041-1-christian.couder@gmail.com> * jc/format-patch-force-in-body-from (2022-08-29) 3 commits (merged to 'next' on 2022-09-05 at cecaaad60e) + format-patch: learn format.forceInBodyFrom configuration variable + format-patch: allow forcing the use of in-body From: header + pretty: separate out the logic to decide the use of in-body from "git format-patch --from=" can be told to add an in-body "From:" line even for commits that are authored by the given with "--force-in-body-from"option. source: <20220829213837.13849-1-gitster@pobox.com> * jk/tempfile-active-flag-cleanup (2022-08-30) 3 commits (merged to 'next' on 2022-09-05 at 43ed4656b3) + tempfile: update comment describing state transitions + tempfile: drop active flag + Merge branch 'rs/tempfile-cleanup-race-fix' into jk/tempfile-active-flag-cleanup Code clean-up. source: * js/add-p-diff-parsing-fix (2022-09-01) 3 commits (merged to 'next' on 2022-09-02 at 1545e0898d) + add -p: ignore dirty submodules + add -p: gracefully handle unparseable hunk headers in colored diffs + add -p: detect more mismatches between plain vs colored diffs Those who use diff-so-fancy as the diff-filter noticed a regression or two in the code that parses the diff output in the built-in version of "add -p", which has been corrected. source: * js/range-diff-with-pathspec (2022-08-26) 3 commits (merged to 'next' on 2022-09-05 at c027222552) + range-diff: optionally accept pathspecs + range-diff: consistently validate the arguments + range-diff: reorder argument handling Allow passing a pathspec to "git range-diff". source: * vd/sparse-reset-checkout-fixes (2022-09-02) 1 commit (merged to 'next' on 2022-09-05 at 8c59ace003) + unpack-trees: fix sparse directory recursion check Segfault fix-up to an earlier fix to the topic to teach "git reset" and "git checkout" work better in a sparse checkout. source: -------------------------------------------------- [New Topics] * ab/doc-synopsis-and-cmd-usage (2022-09-07) 34 commits - tests: start asserting that *.txt SYNOPSIS matches -h output - doc txt & -h consistency: make "worktree" consistent - worktree: define subcommand -h in terms of command -h - reflog doc: list real subcommands up-front - doc txt & -h consistency: make "commit" consistent - doc txt & -h consistency: make "diff-tree" consistent - doc txt & -h consistency: use "[