From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git-for-windows@googlegroups.com, git@vger.kernel.org,
git-packagers@googlegroups.com
Subject: [ANNOUNCE] Git for Windows 2.25.0
Date: Mon, 13 Jan 2020 23:02:05 +0100 (CET) [thread overview]
Message-ID: <1N5VD8-1jkRMd1ES2-016vQB@mail.gmx.com> (raw)
Dear Git users,
It is my pleasure to announce that Git for Windows 2.25.0 is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.24.1(2) (December 10th 2019)
New Features
* Comes with Git v2.25.0.
* Comes with GNU Privacy Guard v2.2.19.
* Comes with Git LFS v2.9.2.
* When upgrading Git for Windows, by default the installer now only
shows pages with previously-unseen options.
* Comes with cURL v7.68.0.
Bug Fixes
* The startup file for GNU nano, which had been included with DOS
line endings (and therefore upset nano) is now included with Unix
line endings again.
* Git for Windows now fails as expected when trying to check out
files with illegal characters in their file names.
* Git now works properly when inside a symlinked work tree.
* Repositories with old commits containing backslashes in file names
can now be fetched/cloned again (but Git will still refuse to check
out files with backslashes in their file names).
* Git GUI can now deal with uninitialized submodules (this was a
Windows-specific bug).
* It is again possible to clone repositories where some past revision
contained file names containing backslashes (Git will of course
still refuse to check out such revisions).
Filename | SHA-256
-------- | -------
Git-2.25.0-64-bit.exe | 6ffb0674a5f5fec2a328dd40456ede87ed3c7de653ecd6950f9cf132bca2f94c
Git-2.25.0-32-bit.exe | 6c02f1a1f95e286df8b87c2812c9460f4c2d333bab7a654751e01e9801994045
PortableGit-2.25.0-64-bit.7z.exe | c191542f68e788f614f8a676460281399af0c9d32f19a5d208e9621dd46264fb
PortableGit-2.25.0-32-bit.7z.exe | 5ad97ff1e806815aa461ab39794e42455f19c9a6ead08ca0e5b8f2bb085214a6
MinGit-2.25.0-64-bit.zip | 30bbd4ba6ca21fe97d43397a3d4e0e24be6ae2660b517cc1b96350195e48adea
MinGit-2.25.0-32-bit.zip | 0075b80e868cff4a00f7d328c9406bd35dbebbd28ef2f5f594dde03e2256a88a
MinGit-2.25.0-busybox-64-bit.zip | cd1e0e2fe8b2dee9e1ffd826501c1453532e01be5739f364a588560b26f6dc91
MinGit-2.25.0-busybox-32-bit.zip | 8edbcef08bdf206c890b7e17bcfb1f355ee6304e9b80445b076200c14efa71c2
Git-2.25.0-64-bit.tar.bz2 | af4cf57901098f3f36a4a75e4c93ce1078553433e69fd7a54b2a872bc8c2c7a1
Git-2.25.0-32-bit.tar.bz2 | 977606f93b58146126dc2c7b7ad19985eaa812852b08dd3354b5e40887cccd34
pdbs-for-git-64-bit-2.25.0.1.7c71c859c9-1.zip | 700f817cc66ae46309d8ad0bf535122b11276e1be67ccd91acfd9b54bf3a6fe5
pdbs-for-git-32-bit-2.25.0.1.7c71c859c9-1.zip | 7ee0a2a2a6a755169821b6e58bf313edf0436bbf26c5cbfb8efc2d7042488ffa
Ciao,
Johannes
reply other threads:[~2020-01-13 22:02 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1N5VD8-1jkRMd1ES2-016vQB@mail.gmx.com \
--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.
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 NNTP newsgroup(s).