git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: git-for-windows@googlegroups.com,  git@vger.kernel.org,
	git-packagers@googlegroups.com
Subject: Re: [ANNOUNCE] Git for Windows 2.49.0-rc1
Date: Wed, 05 Mar 2025 08:00:27 -0800	[thread overview]
Message-ID: <xmqqv7snlb6s.fsf@gitster.g> (raw)
In-Reply-To: <1MmDIo-1tPXph2dbU-00pKOM@mail.gmx.net> (Johannes Schindelin's message of "Wed, 5 Mar 2025 15:52:33 +0100 (CET)")

Johannes Schindelin <johannes.schindelin@gmx.de> writes:

> Dear Git users,
>
> I hereby announce that Git for Windows 2.49.0-rc1 is available from:
>
>     https://github.com/git-for-windows/git/releases/tag/v2.49.0-rc1.windows.1

Thanks, as always.

> 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-rc1.
>   * 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.
>
> Git-2.49.0-rc1-64-bit.exe | 81bf3f20c85c0ca82de760da8ac28eec53523edfb24a7c71f925e1c1e11bbe40
> Git-2.49.0-rc1-arm64.exe | 1b527f8e80c10a09d561908fd8cbe8acefb47bd1f61da5048188808deed64183
> PortableGit-2.49.0-rc1-64-bit.7z.exe | b387c7ae0ce0eb751e5ca812fd47dddc8b53f0cc1148b4ba67b66071e5933f1d
> PortableGit-2.49.0-rc1-arm64.7z.exe | 80a7a186150ff22b695e54b20e55684f6c1a6abeaf2f32c9c256263a8901465d
> MinGit-2.49.0-rc1-64-bit.zip | bc0d31dcb8a04eb5b0645ef92f132c3e3b184817b3d840806c06accb51e47ef7
> MinGit-2.49.0-rc1-arm64.zip | c0244edc063ccb23aa425c88a591d2e90e6967725e168070ca64aea55e78ebb1
> MinGit-2.49.0-rc1-32-bit.zip | b7edc701e8b874bca635896e0e9653bf1be5f6098d7046120c9a1a9af2f7844f
> MinGit-2.49.0-rc1-busybox-64-bit.zip | dbeef21bf998c8094a936180251b51731040fccd0fa414c68a37b475b2ecebea
> MinGit-2.49.0-rc1-busybox-32-bit.zip | aa516fe9904c406c29d9f030e80bf17de08aae009124fffad0249afd669da756
> Git-2.49.0-rc1-64-bit.tar.bz2 | 65c1104bda7fa199829967a3f941c482721b983ffdb1132e76d2282a0e3f8c01
> Git-2.49.0-rc1-arm64.tar.bz2 | 528e9c6759f30367e2cac04231c141d7973240ed7212d521bd2495d25878736a
>
> Ciao,
> Johannes

      reply	other threads:[~2025-03-05 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 14:52 [ANNOUNCE] Git for Windows 2.49.0-rc1 Johannes Schindelin
2025-03-05 16:00 ` 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=xmqqv7snlb6s.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git-for-windows@googlegroups.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).