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 Mailing List <git@vger.kernel.org>
Subject: Git for Windows 2.5.1 is out
Date: Mon, 31 Aug 2015 10:54:58 +0200	[thread overview]
Message-ID: <44a7997123f03bb4d5f47724befd8417@www.dscho.org> (raw)

Dear Git (for Windows) users,

it is my pleasure to announce the release of Git for Windows 2.5.1. Apart from synchronizing with Git 2.5.1, the following bugs were fixed:

  • Backspace works now with ConHost-based (cmd.exe) terminal.
  • When there is a ~/.bashrc but no ~/.bash_profile, the latter will be
    created automatically.
  • When calling a non-login shell, the prompt now works.
  • The text in the installer describing the terminal emulator options is no
    longer cut off.
  • The connect.exe tool to allow SSH connections via HTTP/HTTPS/SOCKS proxies
    is included in Git for Windows again, as it was in Git for Windows 1.x.
  • The LANG variable is no longer left unset (which caused troubles with vim).
  • `call start-ssh-agent` no longer spits out bogus lines.
  • It is now possible even behind NTLM-authenticated proxies to install Git
    for Windows' SDK.
  • We can handle the situation now when the first $PATH elements point outside
    of Git for Windows' bin/ directories and contain .dll files that interfere
    with our own (e.g. PostgreSQL's libintl-8.dll).
  • The patch tool is now included again as it was in Git for Windows 1.x.

Ciao,
Johannes

             reply	other threads:[~2015-08-31  8:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  8:54 Johannes Schindelin [this message]
     [not found] ` <b294f2d7-5e76-4c49-8033-5e0001b79e52@googlegroups.com>
2015-09-02 23:16   ` [git-for-windows] Re: Git for Windows 2.5.1 is out Johannes Schindelin

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=44a7997123f03bb4d5f47724befd8417@www.dscho.org \
    --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.
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).