From: Junio C Hamano <gitster@pobox•com>
To: git@vger•kernel.org
Subject: preparing for 2.34.1
Date: Mon, 22 Nov 2021 09:37:15 -0800 [thread overview]
Message-ID: <xmqqr1b8gkhg.fsf@gitster.g> (raw)
There are a few topics [*] to fix regressions introduced in the
previous cycle, which should be in 2.34.1 and I've merged them to
'master'. I hope we can merge them to 'maint' (which now point at
2.34) and tag 2.34.1 in a few days.
After that, in yet another few days, we will see most of the stalled
topics ejected from the tree, the tip of 'next' rewound, and we will
start the cycle toward 2.35 by starting to take new topics, by the
beginning of the next week at the latest.
Thanks.
* ab/update-submitting-patches (2021-11-13) 1 commit
(merged to 'next' on 2021-11-19 at b44f4d0eb0)
+ SubmittingPatches: fix Asciidoc syntax in "GitHub CI" section
Doc fix.
* ev/pull-already-up-to-date-is-noop (2021-11-18) 1 commit
(merged to 'next' on 2021-11-19 at 2d8f0cd000)
+ pull: should be noop when already-up-to-date
"git pull" with any strategy when the other side is behind us
should succeed as it is a no-op, but doesn't.
* hm/paint-hits-in-log-grep (2021-11-19) 1 commit
(merged to 'next' on 2021-11-19 at e146d25c7c)
+ Revert "grep/pcre2: fix an edge case concerning ascii patterns and UTF-8 data"
"git grep" looking in a blob that has non-UTF8 payload was
completely broken when linked with certain versions of PCREv2
library in the latest release.
next reply other threads:[~2021-11-22 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 17:37 Junio C Hamano [this message]
2021-11-22 20:51 ` preparing for 2.34.1 Carlo Arenas
2021-11-22 22:28 ` Johannes Schindelin
2021-11-22 22:42 ` Junio C Hamano
2021-11-22 23:30 ` Johannes Schindelin
2021-11-22 23:51 ` rsbecker
2021-11-22 22:50 ` Carlo Arenas
2021-11-22 21:50 ` Derrick Stolee
2021-11-22 22:45 ` Junio C Hamano
2021-11-23 17:18 ` preparing for 2.34.1 (2nd round) 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqr1b8gkhg.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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