git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git-for-windows@googlegroups.com, git@vger.kernel.org,
	git-packagers@googlegroups.com
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: [ANNOUNCE] Git for Windows 2.19.0
Date: Thu, 13 Sep 2018 02:23:44 +0000	[thread overview]
Message-ID: <20180913022344.1348-1-johannes.schindelin@gmx.de> (raw)

Dear Git users,

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

	https://gitforwindows.org/

Changes since Git for Windows v2.18.0 (June 22nd 2018)

New Features

  * Comes with Git v2.19.0.
  * There are now fast, built-in versions of git stash and git rebase,
    available as experimental options.
  * The included OpenSSH client now enables modern ciphers.
  * The gitweb component was removed because it is highly unlikely to
    be used on Windows.
  * The git archimport tool (which was probably used by exactly 0
    users) is no longer included in Git for Windows.
  * Comes with tig v2.4.0.
  * Comes with Git LFS v2.5.1.
  * Comes with Git Credential Manager v1.17.1.
  * Comes with OpenSSL v1.0.2p.
  * Comes with cURL v7.61.1.
  * Comes with mingw-w64-nodejs v8.12.0.

Bug Fixes

  * The http.schannel.checkRevoke setting (which never worked) was
    renamed to http.schannelCheckRevoke. In the same run,
    http.schannel.useSSLCAInfo (which also did not work, for the same
    reason) was renamed to http.schannelUseSSLCAInfo.
  * Avoids a stack overflow with recent Windows Insider versions.
  * Git GUI now handles hooks correctly in worktrees other than the
    main one.
  * When using core.autocrlf, the bogus "LF will be replaced by CRLF"
    warning is now suppressed.
  * The funny fatal error -cmalloc would have returned NULL problems
    should be gone.

Filename | SHA-256
-------- | -------
Git-2.19.0-64-bit.exe | 2dd5824e29ca44e86016cdb3dae8446cb5b80b77f596b67e3d8754451fa4bbcb
Git-2.19.0-32-bit.exe | 66b29edc994838586e141b07394900426d59d86a3126cddc04d9ab26032eb7b4
PortableGit-2.19.0-64-bit.7z.exe | 1b8761ae57f589890a83995d0da7891efbddfee14e9f0c3ffda91f6add5b9351
PortableGit-2.19.0-32-bit.7z.exe | edaeb1962b7620bff33d45889eb4bcb6e4ac95021042910871b6025515785c16
MinGit-2.19.0-64-bit.zip | 424d24b5fc185a9c5488d7872262464f2facab4f1d4693ea8008196f14a3c19b
MinGit-2.19.0-32-bit.zip | 83cf018bd6f5c24e2b3088539bbeef9067fd632087d094d447a3a0ff676e7bd7
MinGit-2.19.0-busybox-64-bit.zip | 128b355e4321dbaf699ff4994ddbb6cde92783f4930be50aad507f6d8dbec0d0
MinGit-2.19.0-busybox-32-bit.zip | 2695578e2c53f32194986456ce714388149d051041f638e9ed43dd8342465fb2
Git-2.19.0-64-bit.tar.bz2 | c3ca6f9f2b6b800ade80ee4973cdaed9869b8c2c684c9a6a0940d5fb1e18bef7
Git-2.19.0-32-bit.tar.bz2 | 6f8426646e68ea2689b6a1cfc09ba221805f21540e7dc7af00335f27d3b333b8
pdbs-for-git-64-bit-2.19.0.1.d96bb8bc6c-1.zip | 5f4417ab5b362823b416ead4960e8050682349b603af9ef653bacbbb7eea408a
pdbs-for-git-32-bit-2.19.0.1.d96bb8bc6c-1.zip | 157f78f63d8df39b1ae6dedfcafbe1a9093a1fcc4768b123dae12ee2ae8c82c5

Ciao,
Johannes

                 reply	other threads:[~2018-09-13  2:23 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 \
    --in-reply-to=20180913022344.1348-1-johannes.schindelin@gmx.de \
    --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.
Code repositories for project(s) associated with this public 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).