git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: Peter Olsson <peter@olssononline.se>, git@vger.kernel.org
Subject: Re: Problem with Integrated Vim Editor on Win 10
Date: Thu, 31 Mar 2016 08:49:39 +0200	[thread overview]
Message-ID: <1459406979.21328.14.camel@kaarsemaker.net> (raw)
In-Reply-To: <loom.20160331T083046-590@post.gmane.org>

On do, 2016-03-31 at 06:33 +0000, Peter Olsson wrote:
> I'm not sure where we should report this?

While the git-for-windows maintainer does read this list, git-for
-windows specific issues should be reported in its issue tracker on
GitHub.

It looks like this issue has been reported already:
https://github.com/git-for-windows/git/issues/711

-- 
Dennis Kaarsemaker
http://www.kaarsemaker.net

  reply	other threads:[~2016-03-31  6:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31  0:07 Problem with Integrated Vim Editor on Win 10 Zachary Turner
2016-03-31  6:03 ` Theo Niessink
2016-03-31  6:33 ` Peter Olsson
2016-03-31  6:49   ` Dennis Kaarsemaker [this message]
2016-03-31 17:20 ` Zachary Turner
2016-03-31 17:48   ` Konstantin Khomoutov
2016-03-31 18:41   ` Philip Oakley
2016-03-31 18:59   ` Junio C Hamano

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=1459406979.21328.14.camel@kaarsemaker.net \
    --to=dennis@kaarsemaker.net \
    --cc=git@vger.kernel.org \
    --cc=peter@olssononline.se \
    /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).