From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: git-packagers@googlegroups.com
Subject: [ANNOUNCE] Git v2.36.1
Date: Fri, 06 May 2022 10:27:28 -0700 [thread overview]
Message-ID: <xmqqczgqmv0f.fsf@gitster.g> (raw)
The latest maintenance release Git v2.36.1 is now available at
the usual places.
This is to fix many of the regressions shipped with v2.36.0;
unfortunately, there still are a few known regressions that are not
yet fixed, which have to wait for future maintenance releases.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/
The following public repositories all have a copy of the 'v2.36.1'
tag and the 'maint' branch that the tag points at:
url = https://git.kernel.org/pub/scm/git/git
url = https://kernel.googlesource.com/pub/scm/git/git
url = git://repo.or.cz/alt-git.git
url = https://github.com/gitster/git
----------------------------------------------------------------
Git v2.36.1 Release Notes
=========================
Fixes since v2.36
-----------------
* "git submodule update" without pathspec should silently skip an
uninitialized submodule, but it started to become noisy by mistake.
* "diff-tree --stdin" has been broken for about a year, but 2.36
release broke it even worse by breaking running the command with
<pathspec>, which in turn broke "gitk" and got noticed. This has
been corrected by aligning its behaviour to that of "log".
* Regression fix for 2.36 where "git name-rev" started to sometimes
reference strings after they are freed.
* "git show <commit1> <commit2>... -- <pathspec>" lost the pathspec
when showing the second and subsequent commits, which has been
corrected.
* "git fast-export -- <pathspec>" lost the pathspec when showing the
second and subsequent commits, which has been corrected.
* "git format-patch <args> -- <pathspec>" lost the pathspec when
showing the second and subsequent commits, which has been
corrected.
* Get rid of a bogus and over-eager coccinelle rule.
* Correct choices of C compilers used in various CI jobs.
Also contains minor documentation updates and code clean-ups.
----------------------------------------------------------------
Changes since v2.36.0 are as follows:
Junio C Hamano (4):
2.36 gitk/diff-tree --stdin regression fix
2.36 show regression fix
cocci: drop bogus xstrdup_or_null() rule
Git 2.36.1
Orgad Shaneh (1):
submodule--helper: fix initialization of warn_if_uninitialized
René Scharfe (3):
Revert "name-rev: release unused name strings"
2.36 format-patch regression fix
2.36 fast-export regression fix
Ævar Arnfjörð Bjarmason (1):
CI: select CC based on CC_PACKAGE (again)
reply other threads:[~2022-05-06 17:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=xmqqczgqmv0f.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git-packagers@googlegroups.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).