From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2021, #05; Wed, 17)
Date: Thu, 18 Mar 2021 18:53:51 -0700 [thread overview]
Message-ID: <xmqqblbfq574.fsf@gitster.g> (raw)
In-Reply-To: <xmqqblbhtoa6.fsf@gitster.g> (Junio C. Hamano's message of "Wed, 17 Mar 2021 15:21:05 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> 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.
A few topics that are relevant for 2.31.x maintenance track have
been merged to 'next', and I am planning to merge the following
topics (including those that are new in 'next' due to their being
maint material) down to 'master' before doing anything else, before
the beginning of the next week at the latest.
After that, let's rewind the tip of 'next' and start merging other
topics down to 'next', but that will still be done as-time-permits
basis and the progress may be slow yet.
+ ab/remote-write-config-in-camel-case 02-24/03-01 #2
+ mt/cleanly-die-upon-missing-required-filter 02-26/03-01 #1
+ jk/perf-in-worktrees 02-26/03-02 #2
+ dl/cat-file-doc-cleanup 03-03/03-13 #2
+ jr/doc-ignore-typofix 03-03/03-13 #1
+ sv/t9801-test-path-is-file-cleanup 03-03/03-13 #1
+ ah/make-fuzz-all-doc-update 03-08/03-13 #1
+ rr/mailmap-entry-self 03-08/03-13 #1
+ ps/update-ref-trans-hook-doc 03-01/03-14 #2
+ tb/git-mv-icase-fix 03-03/03-14 #1
+ rs/xcalloc-takes-nelem-first 03-08/03-14 #1
+ bc/clone-bare-with-conflicting-config 03-10/03-14 #1
+ jk/slimmed-down 03-14/03-18 #1
+ jc/calloc-fix 03-15/03-18 #1
+ rs/calloc-array 03-15/03-18 #3
+ jh/fsmonitor-prework 03-17/03-18 #1
+ jk/bisect-peel-tag-fix 03-17/03-18 #1
+ js/fsmonitor-unpack-fix 03-17/03-18 #2
+ jt/clone-unborn-head 03-17/03-18 #1
+ km/config-doc-typofix 03-17/03-18 #1
+ rs/avoid-null-statement-after-macro-call 03-17/03-18 #2
prev parent reply other threads:[~2021-03-19 1:54 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
[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 [this message]
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=xmqqblbfq574.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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).