From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Duy Nguyen <pclouds@gmail.com>
Cc: git-for-windows@googlegroups.com, Git Mailing List <git@vger.kernel.org>
Subject: Re: On a personal note
Date: Thu, 17 Sep 2015 20:54:49 +0200 [thread overview]
Message-ID: <a6ea2cc0231a0fc311b45b8d6edbd305@dscho.org> (raw)
In-Reply-To: <CACsJy8AcK8hAkMowA0t5SusJDTYZDWZCFN5JDs2f-puZcJAfhg@mail.gmail.com>
Hi Duy,
On 2015-09-17 15:29, Duy Nguyen wrote:
> On Thu, Sep 3, 2015 at 5:00 PM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
>>
>> yes, it is true: since mid-August I am working for Microsoft. Over a
>> year ago, I got into contact with the Visual Studio Online group at
>> Microsoft, of which I am now a happy member. A large part of my mission
>> is to improve the experience of Git for Windows. This is very exciting
>> to me: I finally can focus pretty much full time on something that I
>> could only address in my spare time previously.
>
> Is upstreaming msysgit-specific patches in the roadmap? It would be
> very nice to have everything in one tree (or at least keep the two
> trees as close as possible).
Please strike that name "msysgit" from your memory. Just remember "Git for Windows". (The name "msysgit" *never* referred to "Git for Windows", but only to the development environment used to generate Git for Windows 1.x). Please. Thank you.
And yes, the roadmap is pretty clear from the GitHub tickets, e.g. this one:
https://github.com/git-for-windows/git/issues/285
Please note that I held off this week for three reasons:
1) I was submitting patches to the MSys2 and Cygwin upstream first,
2) I was busy fixing e.g. that bug where home directories containing non-ASCII characters were handled incorrectly (and generally trying to keep the tickets in https://github.com/git-for-windows/git under something similar to control), and
3) what with Peff's and Stefan's huge patch series, I did not want to overload Junio.
Please note that I already started submitting patches, though:
http://thread.gmane.org/gmane.comp.version-control.git/277542
http://article.gmane.org/gmane.comp.version-control.git/277731
Ciao,
Dscho
next prev parent reply other threads:[~2015-09-17 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 10:00 On a personal note Johannes Schindelin
2015-09-04 12:43 ` Steve Hoelzer
2015-09-04 13:08 ` Jeff King
2015-09-04 16:10 ` Junio C Hamano
[not found] ` <CACwWb3B-8iNhXXWo0N5whDy8pwUCyr5fA2SZuxP=tYd3jWB0SQ@mail.gmail.com>
2015-09-06 16:45 ` Johannes Schindelin
2015-09-17 13:29 ` Duy Nguyen
2015-09-17 18:54 ` Johannes Schindelin [this message]
2015-09-17 19:27 ` Stefan Beller
2015-09-18 10:32 ` Windows patches roadmap, was " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a6ea2cc0231a0fc311b45b8d6edbd305@dscho.org \
--to=johannes.schindelin@gmx.de \
--cc=git-for-windows@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
/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).