From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2019, #05; Thu, 30)
Date: Fri, 31 May 2019 13:39:30 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1905311337270.44@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqwoi7ws9z.fsf@gitster-ct.c.googlers.com>
Hi Junio,
On Thu, 30 May 2019, Junio C Hamano wrote:
> Here are the topics that have been cooking. Commits prefixed with
> '-' are only in '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.
>
> The second round of release candidate has been tagged, after
> slipping for several days to merge a handful of last-minute
> regression fixes.
You hinted in an earlier "What's cooking" that you'd maybe go for an -rc3.
Is that still the case?
Or for that matter: do you plan on releasing a v2.21.1 before v2.22.0?
Ciao,
Dscho
P.S.: As you might have guessed, I would like to know in order to
determine how to proceed with Git for Windows' `master`: whether to hop on
the v2.22.x train or whether to stay on the v2.21.x train just a little
longer.
next prev parent reply other threads:[~2019-05-31 11:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 21:23 What's cooking in git.git (May 2019, #05; Thu, 30) Junio C Hamano
2019-05-31 11:39 ` Johannes Schindelin [this message]
2019-05-31 17:02 ` Junio C Hamano
2019-05-31 17:14 ` Johannes Schindelin
2019-05-31 12:42 ` Johannes Schindelin
2019-05-31 17:34 ` Junio C Hamano
2019-05-31 18:48 ` Johannes Schindelin
2019-06-01 15:08 ` Kaartic Sivaraam
2019-06-02 17:48 ` Philip Oakley
2019-05-31 18:56 ` Junio C Hamano
2019-05-31 20:26 ` cc/list-objects-filter-wo-sparse-path, was " Johannes Schindelin
2019-06-02 14:32 ` Jiang Xin
2019-06-05 18:38 ` Nickolai Belakovski
2019-06-06 13:09 ` Johannes Schindelin
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=nycvar.QRO.7.76.6.1905311337270.44@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--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).