From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git-for-windows@googlegroups.com, git@vger.kernel.org
Subject: [ANNOUNCE] Git for Windows 2.7.2
Date: Tue, 23 Feb 2016 16:17:58 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1602231617450.3152@virtualbox> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=X-UNKNOWN, Size: 1679 bytes --]
Dear Git users,
It is my pleasure to announce that Git for Windows 2.7.2 is available from:
https://git-for-windows.github.io/
Changes since Git for Windows v2.7.1(2) (February 12th 2016)
New Features
• Git for Windows' SDK version 1.0.2 has been released.
• The "list references" window of gitk is now wider by default.
• Comes with Git 2.7.2.
Bug Fixes
• The user is now presented with a nice error message when calling
node while node.exe is not in the PATH (this bug also affected
other interactive console programs such as python and php).
• The arrow keys are respected again in gitk.
• When a too-long path is encountered, git clean -dfx no longer
aborts quietly.
• Git GUI learned to stage lines appended to a single-line file.
• When launching C:\Program Files\Git\bin\bash -l -i in a cmd window
and pressing Ctrl+C, the console is no longer corrupted
(previously, the bash.exe redirector would terminate and both cmd &
Bash would compete for user input).
Filename | SHA-256
-------- | -------
Git-2.7.2-64-bit.exe | ec4009b36ce855ab262f999030fff5471de73cf0071202138d395648756c7e8b
Git-2.7.2-32-bit.exe | 7b432c88fa7ced6a89670e9672279e875361651a0abcddbac6fea64a1a168022
PortableGit-2.7.2-64-bit.7z.exe | 774e18aa40a35ce5f3c0002038937e341c625292c474641c8c936822ef77e949
PortableGit-2.7.2-32-bit.7z.exe | 26d1e4a290a5741bccc944684a2ffc664676ccc9571e6077d1b8ab40a31fae18
Git-2.7.2-64-bit.tar.bz2 | b292c68ede2b526db47692ec086b7eea61371bc9548c70e19f25f8625bd87242
Git-2.7.2-32-bit.tar.bz2 | d9c2cbae64f3c581b497d2adddfa70502ae18436a222d4817c0597c889ee8d09
Ciao,
Johannes
reply other threads:[~2016-02-23 15:18 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1602231617450.3152@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git-for-windows@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.
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).