From: Junio C Hamano Date: Fri, 28 Oct 2022 22:06:46 +0000 (-0700) Subject: What's cooking (2022/10 #08) X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c6435b135c12430e8c99d879da65ed6e4e88c02a;p=thirdparty%2Fgit.git What's cooking (2022/10 #08) --- diff --git a/whats-cooking.txt b/whats-cooking.txt index fe3ae70d2a..aef62a5181 100644 --- a/whats-cooking.txt +++ b/whats-cooking.txt @@ -1,10 +1,10 @@ To: git@vger.kernel.org -Subject: What's cooking in git.git (Oct 2022, #07; Wed, 26) -X-master-at: c6de66bd952dbf9e155871be60e3eb5a0439dac9 -X-next-at: 7bbb16d38b18ad93d53518b845d432a38daad2ef +Subject: What's cooking in git.git (Oct 2022, #08; Fri, 28) +X-master-at: 63bba4fdd86d80ef061c449daa97a981a9be0792 +X-next-at: 37b22c650d22cf3ee7c1d89d0a08614485da773a Bcc: lwn@lwn.net, gitster@pobox.com -What's cooking in git.git (Oct 2022, #07; Wed, 26) +What's cooking in git.git (Oct 2022, #08; Fri, 28) -------------------------------------------------- Here are the topics that have been cooking in my tree. Commits @@ -14,31 +14,10 @@ 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. -The security releases are over, and we have enough accumulated fixes -on the 'master' front, I've merged a handful of them to 'maint'. We -may or may not have a 2.38.2 release before we conclude this cycle. -We'll see what happens. - Starting from next week (week #4---see https://tinyurl.com/gitCal), we'll try a mini "bus factor" exercise, where I will disappear from -the list for a few weeks. Taylor agreed to volunteer as an interim -maintainer and will take over the daily integration of the project -in the meantime. The branches at https://github.com/git/git/ -repository will be updated to reflect the result of daily -integration cycles by the interim maintainer during the exercise. - -Other repositories would not be (see below). Most importantly, the -kernel.org one will be likely left stale. But the interim -maintainer may choose to publish to other repositories and announce -them on this list. One that may be handy to have is a repository as -a replacement for https://github.com/gitster/git/ repository that -hosts "broken out" topics. - -Around week #7, I'll come back and we will conclude the exercise. -Note that the interim maintainer will really make decisions on what -topics to accept and advance to 'next' and 'master' in these weeks, -and I will accept these decisions when I come back and continue from -there. +the list for a few weeks. See the previous issue of this report +for details: https://lore.kernel.org/git/xmqqwn8mh1di.fsf@gitster.g/ 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 @@ -71,105 +50,412 @@ Release tarballs are available at: -------------------------------------------------- [Graduated to 'master'] -* ab/grep-simplify-extended-expression (2022-10-11) 1 commit - (merged to 'next' on 2022-10-13 at 07993f09bc) - + grep.c: remove "extended" in favor of "pattern_expression", fix segfault +* ab/doc-synopsis-and-cmd-usage (2022-10-13) 34 commits + (merged to 'next' on 2022-10-21 at c6d632ac1a) + + tests: assert consistent whitespace in -h output + + 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 "[