git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: <stefan.naewe@atlas-elektronik.com>
To: <Johannes.Schindelin@gmx.de>, <git-for-windows@googlegroups.com>,
	<git@vger.kernel.org>, <git-packagers@googlegroups.com>
Subject: Re: [ANNOUNCE] Git for Windows 2.15.1(2), was Re:Git for Windows 2.15.1
Date: Thu, 30 Nov 2017 07:57:06 +0000	[thread overview]
Message-ID: <115728c6-4b49-7f16-695e-8ad34aaa1e2b@atlas-elektronik.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1711300245250.6482@virtualbox>

Am 30.11.2017 um 02:50 schrieb Johannes Schindelin:
> Hi all,
> 
> unfortunately, a last-minute bug slipped in: MSYS2 updated vim (including
> its defaults.vim, in a way that interacted badly with Git for Windows'
> configuration). The result was that an ugly warning is shown every time a
> user opens vim 

But only if the user doesn't have a ~/.vimrc file!

> (which is still the default editor of Git for Windows, for
> historical reasons).> 
> Git for Windows v2.15.1(2) fixes just this one bug, and can be downloaded
> here:
> 
> 	https://github.com/git-for-windows/git/releases/tag/v2.15.1.windows.2
> 
> Ciao,
> Johannes

Stefan
-- 
----------------------------------------------------------------
/dev/random says: Ignorance can be cured. Stupid is forever.
python -c "print '73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')" 
GPG Key fingerprint = 2DF5 E01B 09C3 7501 BCA9  9666 829B 49C5 9221 27AF

      reply	other threads:[~2017-11-30  8:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 13:57 [ANNOUNCE] Git for Windows 2.15.1 Johannes Schindelin
2017-11-30  0:06 ` Igor Djordjevic
2017-11-30  1:44   ` Johannes Schindelin
2017-11-30  1:50 ` [ANNOUNCE] Git for Windows 2.15.1(2), was " Johannes Schindelin
2017-11-30  7:57   ` stefan.naewe [this message]

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=115728c6-4b49-7f16-695e-8ad34aaa1e2b@atlas-elektronik.com \
    --to=stefan.naewe@atlas-elektronik.com \
    --cc=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).