From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: git@vger.kernel.org, git-packagers@googlegroups.com
Subject: Re: [ANNOUNCE] Git for Windows 2.49.0
Date: Mon, 17 Mar 2025 10:03:36 -0700 [thread overview]
Message-ID: <xmqqwmcna8t3.fsf@gitster.g> (raw)
In-Reply-To: <1MSbxD-1tn8ja1MCn-00W0XL@mail.gmx.net> (Johannes Schindelin's message of "Mon, 17 Mar 2025 11:34:02 +0100 (CET)")
Johannes Schindelin <johannes.schindelin@gmx.de> writes:
> Dear Git users,
>
> I hereby announce that Git for Windows 2.49.0 is available from:
>
> https://gitforwindows.org/
Thanks.
> Changes since Git for Windows v2.48.1 (February 13th 2025)
>
> Due to persistent maintenance challenges and the community's limited
> engagement and usage, git svn support in Git for Windows will be phased
> out over the next few months.
>
> Git for Windows v2.48.1 was the last version to ship with the i686
> ("32-bit") variant of the installer, portable Git and archive. Only
> 32-bit MinGit will be built for future versions, until April 2029.
>
> New Features
>
> * Comes with Git v2.49.0.
> * Comes with OpenSSH v9.9.P2.
> * Comes with PCRE2 v10.45.
> * The previously-experimental --full-name-hash option has been
> accepted into upstream Git as --name-hash-version=2 and is no
> longer experimental.
> * The git backfill command has been accepted into upstream Git; Its
> --batch-size=<n> option has been renamed to --min-batch-size=<n>,
> though.
>
> Bug Fixes
>
> * A change in upstream Git v2.48.0 broke renaming symlinks, which was
> fixed.
> * On a recent Insider Windows version, users experienced the message:
> "Cygwin WARNING: Couldn't compute FAST_CWD pointer", which has been
> fixed.
> * A bug has been fixed that, when calling git add -p from VS Code's
> internal terminal, after using the edit command, caused the
> internal terminal got stuck and no further command was accepted.
> * The syntax highlighting of the nano editor was recently disabled in
> Git for Windows by mistake, which was fixed.
>
> Git-2.49.0-64-bit.exe | 726056328967f242fe6e9afbfe7823903a928aff577dcf6f517f2fb6da6ce83c
> Git-2.49.0-arm64.exe | 490ea5c2a1cb3ca4071079e262d1cba9331252cad1b76f9df1e89f04a09e761b
> PortableGit-2.49.0-64-bit.7z.exe | bc980a64e875304ea5aa88386fda37e8a0089d0f2023616b9995b1ca75b471dd
> PortableGit-2.49.0-arm64.7z.exe | 8fa7e49b319b1109173a90a110aaeb0e9004600ff2ed44adc7dfe56ab21e4148
> MinGit-2.49.0-64-bit.zip | 971cdee7c0feaa1e41369c46da88d1000a24e79a6f50191c820100338fb7eca5
> MinGit-2.49.0-arm64.zip | 847bbe519443cd24c716f490a769056a35f42474cafb757663e1dceca159e911
> MinGit-2.49.0-32-bit.zip | 6d6439436d537624f619ffbf5dba49bcdc4ee1219c5c2756277669928fba2b74
> MinGit-2.49.0-busybox-64-bit.zip | 600d27b4ed7d86f9bc908c3e6563cfdd14f746dee1e91d5f714bfc9e7472cfb1
> MinGit-2.49.0-busybox-32-bit.zip | a6f1b25a1c910381b0886ff37baa3d77d3b662e0a54114ca19244a3f3e9381b6
> Git-2.49.0-64-bit.tar.bz2 | 6c5d66e3dd6cd44e50ba7892e9e24ace57934f277a3424c9702a400b3fedc1eb
> Git-2.49.0-arm64.tar.bz2 | 48109aaccc5387df498c6b91e5f25c27201dac80b62cae3c576d922b3129a66e
>
> Ciao,
> Johannes
prev parent reply other threads:[~2025-03-17 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 10:34 [ANNOUNCE] Git for Windows 2.49.0 Johannes Schindelin
2025-03-17 17:03 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqwmcna8t3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
/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).