From: Johannes Schindelin <email@example.com> To: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Cc: Johannes Schindelin <email@example.com> Subject: [ANNOUNCE] Git for Windows 2.33.1 Date: Wed, 13 Oct 2021 23:43:15 +0000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) Dear Git users, I hereby announce that Git for Windows 2.33.1 is available from: https://gitforwindows.org/ Changes since Git for Windows v2.33.0(2) (August 24th 2021) New Features * Comes with Git v2.33.1. * Comes with OpenSSL v1.1.1l. * The included git svn now uses subversion v1.14.1 internally. * Git Credential Manager for Windows (which was superseded by Git Credential Manager Core, and was deprecated for a long time now, and no longer succeeds to authenticate with GitHub) is no longer included in Git for Windows. * Comes with cURL v7.79.1. * Comes with OpenSSH v8.8p1. * Comes with Git LFS v3.0.1. * The built-in filesystem watcher ("FSMonitor") has been updated to the latest version. * Comes with Git Credential Manager Core v2.0.567.18224. Bug Fixes * Wordpad can be configured as Git's preferred editor again. * A bug where Git's garbage collection during a git pull failed to delete obsolete files was fixed. * The git svn command, which was broken in Git for Windows v2.33.0(2) , has been fixed. * The password prompt when cloning via SSH works again. * The MSYS2 runtime no longer complains about FAST_CWD on Windows/ ARM64. * When VS Code is configured as editor, it no longer needs the window to be closed, just the tab. * The 32-bit versions of Git for Windows included outdated versions of ca-certificates and less, which has been rectified. Git-2.33.1-64-bit.exe | b1b69fcf56d50199536f7e6fc79b75ab16734d4d9a4b85c8e931596f02dd0688 Git-2.33.1-32-bit.exe | bc2ca8f6ffcc6914ed04cfb13b2d0b6b994bd2437283cb3b43188b969bd5ef8b PortableGit-2.33.1-64-bit.7z.exe | 723c879eb447583b893aa3234eae8caaa77d9d3ecf90883271fba98e8b2d99ac PortableGit-2.33.1-32-bit.7z.exe | fad2f32a3ca6e39cfbf7258c485a5601b0bfb620f44c582c1ba22784dd3faad3 MinGit-2.33.1-64-bit.zip | 8c28cde02668bfa3b117a49fe85728c1c8244d21701d5ab675668fc4677c4c7f MinGit-2.33.1-32-bit.zip | f340a3433c2c782ff8724707b87769d15519030d1a0e1c1314255f98eaa4f42f MinGit-2.33.1-busybox-64-bit.zip | 96e2e9c8561eb20a3982fe292d4795bd4c09705f93cc03cf45a2f6b880fba181 MinGit-2.33.1-busybox-32-bit.zip | 3cd68aa4691202f2a182f8e0bf5a8eda2b795fbc6074de3e3c55548efdf28d15 Git-2.33.1-64-bit.tar.bz2 | 1a002a49bc25e51b4571d35d5470a373fa7e0d2c7a6de81573c2d485063f066d Git-2.33.1-32-bit.tar.bz2 | 712a23a9c153402a75b88ec8ca5f51f4a75be6af3ef6ef965d9ed508d3a9a205 Ciao, Johannes
reply other threads:[~2021-10-13 23:43 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [ANNOUNCE] Git for Windows 2.33.1' \ /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
Code repositories for project(s) associated with this 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).