git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (May 2025, #08; Tue, 27)

From
Jean-Noël AVILA <jn.avila@free.fr>
Date
May 28, 2025, 21:01 UTC
Message-ID
<12673686.O9o76ZdvQC@cayenne>
In-Reply-To
<xmqqfrgptv10.fsf@gitster.g>
On Wednesday, 28 May 2025 02:54:03 CEST Junio C Hamano wrote:
Show 57 quoted lines
> 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 and may be annotated with an URL
> to a message that raises issues but they are no means exhaustive.  A
> topic without enough support may be discarded after a long period of
> no activity (of course they can be resubmit when new interests
> arise).
> 
> 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-scm/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]
> 
> * ja/doc-synopsis-style (2025-05-27) 9 commits
>  - doc: convert git-switch manpage to new synopsis style
>  - doc: convert git-mergetool options to new synopsis style
>  - doc: convert git-mergetool manpage to new synopsis style
>  - doc: switch merge config description to new synopsis format
>  - doc: convert merge strategies to synopsis format
>  - doc: merge-options.adoc remove a misleading double negation
>  - doc: convert merge options to new synopsis format
>  - doc: convert git-merge manpage to new style
>  - doc: convert git-checkout manpage to new style
> 
>  Doc mark-up fixes.
> 
>  Will merge to 'next'?
>  source: <pull.1927.git.1748204829.gitgitgadget@gmail.com>
> 

Junio, I haven't seen your series about git-verify-* and others integrated. Are there any remaining points to be fixed?

Thanks,
JN
Previous: Taylor BlauNext: Junio C Hamano
Message 3 of 5 in “What's cooking in git.git (May 2025, #08; Tue, 27)”
  1. Junio C HamanoMay 28, 2025
  2. Taylor BlauMay 28, 2025
  3. Jean-Noël AVILAMay 28, 2025
  4. Junio C HamanoMay 28, 2025
  5. Jean-Noël AVILAMay 29, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.