git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: git-packagers@googlegroups.com
Subject: [ANNOUNCE] Git v2.35.3 and below as a usability fix
Date: Wed, 13 Apr 2022 17:22:05 -0700	[thread overview]
Message-ID: <xmqq1qy04iqa.fsf@gitster.g> (raw)
In-Reply-To: <xmqqv8veb5i6.fsf@gitster.g> (Junio C. Hamano's message of "Tue, 12 Apr 2022 10:01:21 -0700")

The latest maintenance releases Git v2.35.3, together with releases
for older maintenance tracks v2.30.4, v2.31.3, v2.32.2, v2.33.3,
and v2.34.3, are now available at the usual places.

These maintenance releases are to address usability issues in the
recent releases 'v2.35.2', 'v2.34.2', 'v2.33.2', 'v2.32.1',
'v2.31.2', and 'v2.30.3', where each "safe" directory has to be
listed on the safe.directory configuration variables.  A broader
escape hatch has been added so that the value '*' can be used to
declare "my colleagues and their repositories I may ever visit are
all trustworthy".

The same fix appears in the tip of 'master' and all the integration
branches of the project above 'master', too.

The tarballs are found at:

    https://www.kernel.org/pub/software/scm/git/

The following public repositories all have a copy of the tags
mentioned above in the first paragraph.

  url = https://git.kernel.org/pub/scm/git/git
  url = https://kernel.googlesource.com/pub/scm/git/git
  url = https://github.com/gitster/git


Credit for the usability fix goes to Derrick Stolee.



      parent reply	other threads:[~2022-04-14  0:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 17:01 [ANNOUNCE] Git v2.35.2 and below for CVE-2022-24765 Junio C Hamano
2022-04-12 18:05 ` SZEDER Gábor
2022-04-14  0:22 ` 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=xmqq1qy04iqa.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).