From: Junio C Hamano <email@example.com> To: firstname.lastname@example.org Subject: preparing for 2.34.1 (2nd round) Date: Tue, 23 Nov 2021 09:18:46 -0800 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (Junio C. Hamano's message of "Mon, 22 Nov 2021 09:37:15 -0800") Junio C Hamano <email@example.com> writes: 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 day or two. 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, hopefully by the beginning of the next week. Thanks. Fixes since v2.34 ----------------- * "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. * "git pull" with any strategy when the other side is behind us should succeed as it is a no-op, but doesn't. (merge ea1954af ev/pull-already-up-to-date-is-noop later to maint). * An earlier change in 2.34.0 caused JGit application (that abused GIT_EDITOR mechanism when invoking "git config") to get stuck with a SIGTTOU signal; it has been reverted. (merge e3f7e01b50 jc/save-restore-terminal-revert later to maint). * An earlier change that broke .gitignore matching has been reverted. (merge 33c5d6c845 ds/add-rm-with-sparse-index later to maint). * SubmittingPatches document gained a syntactically incorrect mark-up, which has been corrected. (merge edbd9f37 ab/update-submitting-patches later to maint).
prev parent reply other threads:[~2021-11-23 17:18 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-22 17:37 preparing for 2.34.1 Junio C Hamano 2021-11-22 20:51 ` 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 ` 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: preparing for 2.34.1 (2nd round)' \ /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
Code repositories for project(s) associated with this 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).