From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2021, #05; Wed, 17)
Date: Wed, 17 Mar 2021 22:43:25 +0000 [thread overview]
Message-ID: <9047c32c-de07-fae0-263a-0070b2a94ad8@ramsayjones.plus.com> (raw)
In-Reply-To: <xmqqblbhtoa6.fsf@gitster.g>
On 17/03/2021 22:21, Junio C Hamano wrote:
> Here are the topics that have been cooking. Commits prefixed with '-' are
> only in 'seen' (formerly 'pu'---proposed updates) while commits prefixed
> with '+' are in 'next'. The ones marked with '.' do not appear in any of
> the integration branches, but I am still holding onto them.
>
> Git 2.31 has been tagged. We will hopefully either (1) not see
> brown-paper-bag breakages at all, or (2) will see some but can
> immediately deal with them, in coming couple of days. After that,
> the 2.32 cycle will gain steam, starting next week. Let's see.
>
> Many topics marked as "Will cook in 'next'" should be marked for
> merging to 'master' now, but that hasn't happened yet. Please
> nominate those that should be kicked back from 'next' to 'seen', if
> there are any. Please also nominate those that should be among the
> first batch of topics to be in 'master' (after a handful of 2.31
> regression fixes go through 'next' down to 'master', that is).
>
> 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/
Just FYI, the docs repos are still @ v2.31.0-rc2. (I built the
docs locally for this release).
ATB,
Ramsay Jones
next prev parent reply other threads:[~2021-03-17 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 22:21 What's cooking in git.git (Mar 2021, #05; Wed, 17) Junio C Hamano
2021-03-17 22:43 ` Ramsay Jones [this message]
[not found] ` <CAPc5daUBRFvDJzv059usPu89hcXiQELHqyNOhNVzB2aTKnS5aw@mail.gmail.com>
2021-03-17 23:17 ` Ramsay Jones
2021-03-17 23:13 ` Elijah Newren
2021-03-18 22:43 ` Junio C Hamano
2021-03-19 1:04 ` Elijah Newren
2021-03-19 1:53 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9047c32c-de07-fae0-263a-0070b2a94ad8@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).