git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jean-Noël AVILA" <jn.avila@free.fr>
To: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: What's cooking in git.git (May 2025, #08; Tue, 27)
Date: Wed, 28 May 2025 23:01:32 +0200	[thread overview]
Message-ID: <12673686.O9o76ZdvQC@cayenne> (raw)
In-Reply-To: <xmqqfrgptv10.fsf@gitster.g>

On Wednesday, 28 May 2025 02:54:03 CEST Junio C Hamano wrote:
> 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



  parent reply	other threads:[~2025-05-28 21:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28  0:54 What's cooking in git.git (May 2025, #08; Tue, 27) Junio C Hamano
2025-05-28  2:37 ` Taylor Blau
2025-05-28 21:01 ` Jean-Noël AVILA [this message]
2025-05-28 22:02   ` Junio C Hamano
2025-05-29 20:33     ` Jean-Noël AVILA

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=12673686.O9o76ZdvQC@cayenne \
    --to=jn.avila@free.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).