diff --git a/whats-cooking.txt b/whats-cooking.txt index ad5d5f3caa..a9de75bbd3 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 (Mar 2024, #03; Mon, 11) -X-master-at: 945115026aa63df4ab849ab14a04da31623abece -X-next-at: 1203cff8ae1e19af27c286764313c3e3f54ef01e +Subject: What's cooking in git.git (Mar 2024, #04; Fri, 15) +X-master-at: 2953d95d402b6bff1a59c4712f4d46f1b9ea137f +X-next-at: cdc2e80fe5f5dd8f872f21cdcd608126da6ccc7e Bcc: lwn@lwn.net, gitster@pobox.com -What's cooking in git.git (Mar 2024, #03; Mon, 11) +What's cooking in git.git (Mar 2024, #04; Fri, 15) -------------------------------------------------- Here are the topics that have been cooking in my tree. Commits @@ -17,8 +17,6 @@ topic without enough support may be discarded after a long period of no activity (of course they can be resubmit when new interests arise). -The 'maint' branch now points at the 2.44 maintenance track. - 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. @@ -50,427 +48,14 @@ Release tarballs are available at: -------------------------------------------------- [Graduated to 'master'] -* es/config-doc-sort-sections (2024-02-29) 1 commit - (merged to 'next' on 2024-03-04 at 0752144ed7) - + docs: sort configuration variable groupings alphabetically - - Doc updates. - source: <20240229190229.20222-1-ericsunshine@charter.net> - - -* js/merge-base-with-missing-commit (2024-03-09) 13 commits - (merged to 'next' on 2024-03-09 at caa7a7baaa) - + merge-ort/merge-recursive: do report errors in `merge_submodule()` - + merge-recursive: prepare for `merge_submodule()` to report errors - (merged to 'next' on 2024-03-01 at 3e3eabaee9) - + commit-reach(repo_get_merge_bases_many_dirty): pass on errors - + commit-reach(repo_get_merge_bases_many): pass on "missing commits" errors - + commit-reach(get_octopus_merge_bases): pass on "missing commits" errors - + commit-reach(repo_get_merge_bases): pass on "missing commits" errors - + commit-reach(get_merge_bases_many_0): pass on "missing commits" errors - + commit-reach(merge_bases_many): pass on "missing commits" errors - + commit-reach(paint_down_to_common): start reporting errors - + commit-reach(paint_down_to_common): prepare for handling shallow commits - + commit-reach(repo_in_merge_bases_many): report missing commits - + commit-reach(repo_in_merge_bases_many): optionally expect missing commits - + commit-reach(paint_down_to_common): plug two memory leaks - - Originally merged to 'next' on 2024-02-29 - - Make sure failure return from merge_bases_many() is properly caught. - source: - source: - - -* kh/doc-dashed-commands-have-not-worked-for-a-long-time (2024-03-01) 1 commit - (merged to 'next' on 2024-03-04 at 7e070c67f9) - + gitcli: drop mention of “non-dashed form” - - Doc update. - source: <5b34bc4e22816f7f19bd26c15a08fe4c749b72f8.1709316230.git.code@khaugsbakk.name> - - -* rs/t-ctype-simplify (2024-03-03) 4 commits - (merged to 'next' on 2024-03-04 at 9bd84a8877) - + t-ctype: avoid duplicating class names - + t-ctype: align output of i - + t-ctype: simplify EOF check - + t-ctype: allow NUL anywhere in the specification string - - Code simplification to one unit-test program. - source: <20240303101330.20187-1-l.s.r@web.de> - - -* sj/t9117-path-is-file (2024-03-04) 1 commit - (merged to 'next' on 2024-03-04 at de5f6a74cb) - + t9117: prefer test_path_* helper functions - - GSoC practice to replace "test -f" with "test_path_is_file". - source: <20240304095436.56399-2-shejialuo@gmail.com> - --------------------------------------------------- -[New Topics] - -* jc/safe-implicit-bare (2024-03-11) 1 commit - - setup: notice more types of implicit bare repositories - - Users with safe.bareRepository=explicit can still work from within - $GIT_DIR of a seconary worktree (which resides at .git/worktrees/$name/) - of the primary worktree without explicitly specifying the $GIT_DIR - environment variable or the --git-dir= option. - - Will merge to 'next'. - source: - - -* pw/checkout-conflict-errorfix (2024-03-08) 4 commits - - checkout: cleanup --conflict=