From: Junio C Hamano Date: Fri, 09 Sep 2022 23:06:27 GMT Subject: What's cooking in git.git (Sep 2022, #02; Fri, 9) Message-ID: 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 "[