From: Sebastian Schuberth <sschuberth@gmail.com>
To: git@vger.kernel.org
Cc: msysgit@googlegroups.com
Subject: Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows
Date: Sat, 19 Apr 2014 22:56:57 +0200 [thread overview]
Message-ID: <5352E319.2010808@gmail.com> (raw)
In-Reply-To: <rfujmbew27f1gaa6dbk706li.1397911737867@email.android.com>
On 19.04.2014 15:35, Marat Radchenko wrote:
> But in practice, msysgit is:
> 1) outdated msys that was patched in multiple ways without
> sending patches upstream
It's not true that we are not sending patches upstream to MSYS, see [1].
It's just that most of them don't get included due to a lack of time
from the MSYS maintainers, see e.g. [2].
> 2) heavily patched git, again not upstreamed
"Heavily" is relative, in fact it's not that much that I would give up
hope on getting everything upstream. We once had put large efforts in
bringing our stuff to upstream Git, just to over and over again being
pulled into fussy discussions, costing way more time than developing the
patches themselves. So at some time most of us just decided to spend
their time more efficiently by bringing Git for Windows forward.
> To be honest, msys isn't a great tool. After all, it's just outdated
> and heavily patched cygwin. There exists msys2 project (much less outdated and much less patched cygwin).
I agree that MSYS is not at all that great (anymore). It simply does not
seem to be well maintained. But neither do I trust MSYS2 (yet), which
looks to me like a spare time project by one or two guys, both newcomers
not part of the original MSYS team. However, if MSYS2 turns out to be
maintained better than MSYS in the future, I'm open to base
mingwGitDevEnv on MSYS2.
> 1) It makes sense to purge msysgit and start over. See mingwGitDevEnv [2] (by msysgit developer).
You would have been very welcomed to contribute 64-bit support to
mingwGitDevEnv (which I'm the maintainer of). I saddens me that we blow
out our energy on forks (without even getting in touch first) instead of
pulling together.
[1] http://sourceforge.net/p/mingw/bugs/search/?q=msysgit
[2] http://sourceforge.net/p/mingw/bugs/1823/
--
Sebastian Schuberth
next prev parent reply other threads:[~2014-04-19 20:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 13:35 [ANNOUNCE] WinGit - native x86/x64 Git for Windows Marat Radchenko
2014-04-19 17:01 ` Thomas Braun
2014-04-19 17:37 ` Johannes Schindelin
2014-04-19 18:42 ` Heiko Voigt
2014-04-19 21:12 ` Sebastian Schuberth
2014-04-20 22:10 ` [msysGit] " Johannes Schindelin
2014-04-20 22:12 ` Johannes Schindelin
2014-04-21 18:37 ` Sebastian Schuberth
2014-04-21 18:56 ` Johannes Schindelin
2014-04-21 18:56 ` Felipe Contreras
2014-04-21 22:14 ` [NOT_A_PATCH] A naive attempt to cross-build Linux->mingw64 Git Marat Radchenko
2014-04-21 23:59 ` Felipe Contreras
2014-04-22 0:06 ` Felipe Contreras
2014-04-22 13:36 ` Marat Radchenko
2014-04-22 16:08 ` Felipe Contreras
2014-04-22 13:36 ` Johannes Schindelin
2014-04-22 13:14 ` Re: Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows Johannes Schindelin
2014-04-22 14:17 ` David Kastrup
2014-04-22 16:00 ` Re: " Felipe Contreras
2014-04-22 16:14 ` Johannes Schindelin
2014-04-19 20:56 ` Sebastian Schuberth [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-03 13:18 marat
2014-04-03 13:48 ` Konstantin Khomoutov
2014-04-03 14:07 ` Marat Radchenko
2014-04-09 17:27 ` Felipe Contreras
2014-04-19 6:31 ` Heiko Voigt
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=5352E319.2010808@gmail.com \
--to=sschuberth@gmail.com \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.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).