From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git-for-windows@googlegroups.com, git@vger.kernel.org,
git-packagers@googlegroups.com
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: [ANNOUNCE] Git for Windows 2.35.3
Date: Fri, 15 Apr 2022 02:46:44 +0000 [thread overview]
Message-ID: <20220415024644.4908-1-johannes.schindelin@gmx.de> (raw)
Dear Git users,
I hereby announce that Git for Windows 2.35.3 is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.35.2 (April 12th 2022)
New Features
* Comes with Git v2.35.3.
Bug Fixes
* The advice indicating how to use the %(prefix) with a network share
path was updated to use the appropriate number of slashes.
* Various fixes for usage of the safe.directory and %(prefix) when
using Windows Subsystem for Linux (WSL).
Git-2.35.3-64-bit.exe | 5862bd6f4f4619d3bfeb4f9c2cdfdf62fd45658650debd535c6af10a8695e181
Git-2.35.3-32-bit.exe | d6b2bb64f264b5edf014f356ec4f1532128f43ab0c1ecbf43f0d19912d81d0b8
PortableGit-2.35.3-64-bit.7z.exe | 53091932db9ed386a667a4b11b5760bb8eb2d44d556b67cb94fa2766daa37182
PortableGit-2.35.3-32-bit.7z.exe | be28dea2619f0d71872adf3c3f0859838773b3785b7c36f520005e93e4fc1190
MinGit-2.35.3-64-bit.zip | 9b88c81ad796acf9969825e8736b953cb0e0bfb4717be57fd59336ae94d521e4
MinGit-2.35.3-32-bit.zip | 1ad43122a8a7dc1633beeabcfa14aec5c35c211be8f3594431046ce3e60fc542
MinGit-2.35.3-busybox-64-bit.zip | 2b257cdbae25253034fb3f38e13118d951c85e476c32719b0a0d4f1cd7516d69
MinGit-2.35.3-busybox-32-bit.zip | daf08717875ce64fff84cc0ad755ebe209066a02c238eec47994f7b0a8023b1d
Git-2.35.3-64-bit.tar.bz2 | a81ac00b01de762920500b58a631c51be0574d2df50d7a089ef9195a57358a42
Git-2.35.3-32-bit.tar.bz2 | 69a6880ac0171918bd333421141f79bc14097097e35b1f9aacc483f4300c8e08
Ciao,
Johannes
reply other threads:[~2022-04-15 2:47 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=20220415024644.4908-1-johannes.schindelin@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=git-for-windows@googlegroups.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).