From: Derrick Stolee <stolee@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git-packagers@googlegroups.com, Git List <git@vger.kernel.org>
Subject: Re: Git for Windows for Unix?
Date: Thu, 27 Sep 2018 12:18:07 -0400 [thread overview]
Message-ID: <d3d82080-f3e7-50cd-df81-1fed3198eb88@gmail.com> (raw)
In-Reply-To: <87va6rhqup.fsf@evledraar.gmail.com>
On 9/27/2018 12:01 PM, Ævar Arnfjörð Bjarmason wrote:
> I had an IRC conversation with Johannes saying I didn't know Git For
> Windows builds perfectly well for Linux, this just isn't advertised in
> the ANNOUNCE E-Mails, so I hadn't tried.
We run CI to ensure it builds and tests on Mac OSX, too. This is
important to the VFS for Git group, as we work on making that work for
Mac clients. We have our fork of Git for Windows at
https://github.com/microsoft/git.
> GFW is a "friendly fork", but a permanent one it seems. The diff between
> it and 2.19.0 proper is ~10k lines, and e.g. this last release had
> experimental stash/rebase in C that 2.19.0 didn't.
Hopefully we can learn from having this experimental feature in the wild
and improve the patches on-list by fixing issues.
We do have a desire to move as much as possible upstream. It's difficult
to find time to pay down that "fork debt".
Thanks,
-Stolee
prev parent reply other threads:[~2018-09-27 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 16:01 Git for Windows for Unix? Ævar Arnfjörð Bjarmason
2018-09-27 16:05 ` Jonathan Nieder
2018-09-27 16:22 ` Ævar Arnfjörð Bjarmason
2018-09-27 16:26 ` Jonathan Nieder
2018-09-28 19:57 ` Ævar Arnfjörð Bjarmason
2018-09-28 20:42 ` Jonathan Nieder
2018-09-29 15:14 ` Ævar Arnfjörð Bjarmason
2018-09-29 11:19 ` SZEDER Gábor
2018-09-27 16:28 ` Duy Nguyen
2018-09-27 16:18 ` Derrick Stolee [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d3d82080-f3e7-50cd-df81-1fed3198eb88@gmail.com \
--to=stolee@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@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).