From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git-packagers@googlegroups.com, Git List <git@vger.kernel.org>
Subject: Git for Windows for Unix?
Date: Thu, 27 Sep 2018 18:01:18 +0200 [thread overview]
Message-ID: <87va6rhqup.fsf@evledraar.gmail.com> (raw)
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.
Johannes doesn't build his own tarballs, but these are provided at:
https://github.com/git-for-windows/git/tags diffing
https://github.com/git/git/tags v.s. what Junio releases shows:
$ diff -ru git-2.19.0 git-2.19.0.gh
Only in git-2.19.0: configure
Only in git-2.19.0/git-gui: version
Only in git-2.19.0: version
So to use these you need to grab the GitHub tarball, create a "version"
file saying e.g. 2.19.0.windows.1 or whatever it is (derived from the
name of the tarball), and if applicable make your own configure script.
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.
So it would be great if this were packaged up by linux distro as some
"alterate" package of git. I'm putting Jonathan in the "To" line because
I'm mainly interested in this for Debian, but maybe there's wider
interest at git-packagers...
next reply other threads:[~2018-09-27 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 16:01 Ævar Arnfjörð Bjarmason [this message]
2018-09-27 16:05 ` Git for Windows for Unix? 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
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=87va6rhqup.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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).