list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <>
Subject: [ANNOUNCE] Git for Windows 2.22.0
Date: Sat, 8 Jun 2019 16:07:29 +0200 (CEST)	[thread overview]
Message-ID: <> (raw)

Dear Git users,

It is my pleasure to announce that Git for Windows 2.22.0 is available from:

Changes since Git for Windows v2.21.0 (February 26th 2019)

New Features

  * Comes with Git v2.22.0.
  * The awk included in Git for Windows now includes extensions such as
  * The file/product version stored in the installer's .exe file now
    matches the version of the included git.exe file's.
  * Comes with OpenSSH v8.0p1.
  * Comes with Git LFS v2.7.2.
  * Comes with MSYS2 runtime (Git for Windows flavor) based on Cygwin
    v3.x (see release notes for Cygwin 3.0.0, 3.0.1, 3.0.2, 3.0.3,
    3.0.4, 3.0.5, 3.0.6, and 3.0.7).
  * There are now experimental built-in versions of git add -i and git
    add -p, i.e. those modes are now a lot faster (in particular at
    startup). You can opt into using them on the last installer page.
  * PortableGit now comes with a meta credential helper, i.e. a GUI
    that lets the user choose which of the available credential helpers
    to use. This should help to avoid storing credentials on other
    people's machines when running portable Git from a thumb drive.
  * Comes with gawk v5.0.0.
  * Comes with Git Credential Manager v1.19.0.
  * Comes with git-flow v1.12.3.
  * Comes with OpenSSL v1.1.1c.
  * Comes with GNU Privacy Guard v2.2.16, specifically patched to
    handle Windows paths.
  * Comes with cURL v7.65.1.
  * Comes with Heimdal v7.5.0. -packages/pull/33).

Bug Fixes

  * Git for Windows' updater is now accessible, i.e. it can be read by
    a screen reader.
  * git update-git-for-windows (i.e. the auto updater of Git for
    Windows) now reports correctly when it failed to access the GitHub
  * Git for Windows' updater no longer runs into GitHub API rate limits
    (this used to be quite common in enterprise scenarios, where many
    users would share one IP as far as GitHub is concerned).
  * gitk no longer fails with "filename too long" when there are 1,000+
  * A bug which on occasion caused lengthy rebase runs to crash without
    error message was fixed.
  * Two workarounds from the Git for Windows 1.x era (concerning
    reading credentials via GUI and fetching via git://) were
    considered obsolete.
  * git difftool --no-index can now be run outside of Git worktrees.
  * git rebase -i used to get confused when an exec command created new
    commits and then appended pick lines for them. This has been fixed.
  * During a run of git rebase --rebase-merges, the output of git
    status now shows label lines correctly, i.e. with the labels' names
    instead of the commit hash they point to.
  * We now avoid problems updating the commit graph when

Filename | SHA-256
-------- | -------
Git-2.22.0-64-bit.exe | 0c314a62f0f242c64fe1bdae20ab113fef990fb7e3323d0989478b6ed396d00b
Git-2.22.0-32-bit.exe | 9995409d05c6789f96611f9a6365318dd384cb97b94d6d537f13bed789413e18
PortableGit-2.22.0-64-bit.7z.exe | 2d935dc309568a9694711ac080967388c98b69907fb015f6536a4a0920084e0c
PortableGit-2.22.0-32-bit.7z.exe | dee3d963c218b5f7fb0925c5984070f7373abc4c44cf36050fde10bfd3d9bc2e | 308ce95b7de5792bed9d56e1af5d2053052ea6347ea0021f74070056684ce3ee | 61bbb2d02baee1b1c24857b031bae1063e38a3b062a642c0c9304bc80bf7b8fd | 48213aaba43be9b27d45affadcad98a65d06490987500b59e8310ebaed729327 | a5a4634a34cafaff3f7d9340c38d18f2044191a83c2da44fb3ff4db825ff4acd
Git-2.22.0-64-bit.tar.bz2 | e4df1f804512e678bc37b4dc2e0354f9177c0e44fbc73b28ec87702cb34eb236
Git-2.22.0-32-bit.tar.bz2 | 15c1e87cd0a5c100c4c16d6043569eb478c87c4856670c97aeee920c20ea0b84 | e54bb0cd2ae6c0e779065aecd8eeca3ab852781665ca9cfa53207cf136b4f915 | 2e4a1c2024de1b6af6259bfe1dae0d98314c72ca87291fd6a542885954dc6304


                 reply	other threads:[~2019-06-08 14:07 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: [ANNOUNCE] Git for Windows 2.22.0' \

* 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:

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).