git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows

From
Marat Radchenko <marat@slonopotamus.org>
Date
Apr 19, 2014, 13:35 UTC
Message-ID
<rfujmbew27f1gaa6dbk706li.1397911737867@email.android.com>
> So the reason for this new package is that you need 64bit binaries?
That's the most important bit. Plus, weird ssh transfer speeds [1] caused by ansient openssh bundled in msysgit.
> I can see the need for a pure Windows solution (no msys tools at least for runtime).
Several Git scripts are written in perl, many in shell and a couple even in tcl/tk (oh, my). Until this is true, Git requires unix-like userland environment: all those sh, awk, coreutils, findutils and others.
> But this sounds to me that the only thing you changed is the compiler and 64bit?
That would be true *if* msysgit was really msys + mingw-built-git. 
But in practice, msysgit is:
 1) outdated msys that was patched in multiple ways without
  sending patches upstream
 2) heavily patched git, again not upstreamed

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).

So, msysgit is an (outdated patched)*2 cygwin + patched git.
> What is the reason of using a closed source compiler?
It happened to be already installed on my box. Switching to another one will require just minor tweaks to my build script. I don't have any strong reasons for using MSVC.
> Sorry if I am a little bit skeptic, but I am wondering whether it does make sense for you to join forces with msysgit instead of creating a fork?
1) It makes sense to purge msysgit and start over. See mingwGitDevEnv [2] (by msysgit developer).
2)  I only used msys due to my unawareness of msys2 at the time of  initial WinGit hacking. Due to massive Unicode-related msys troubles, ansient perl and svn, I plan to switch to msys2 soon.
> there are no 64 bit binaries shipped with msysgit is that nobody needed them

That's wrong. Google for 'windows x64 git' or 'msysgit x64'. People need it. There's even an issue [3] (stalled several years ago) in msysgit tracker. After all, I needed it.

[1] https://github.com/msysgit/msysgit/issues/31 [2]: https://github.com/sschuberth/mingwGitDevEnv [3]: http://code.google.com/p/msysgit/issues/detail?id=396

Next: Thomas Braun
Message 1 of 21 in “Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows”
  1. Marat RadchenkoApr 19, 2014
  2. Thomas BraunApr 19, 2014
  3. Johannes SchindelinApr 19, 2014
  4. Heiko VoigtApr 19, 2014
  5. Sebastian SchuberthApr 19, 2014
  6. Johannes SchindelinApr 20, 2014
  7. Johannes SchindelinApr 20, 2014
  8. Sebastian SchuberthApr 21, 2014
  9. Johannes SchindelinApr 21, 2014
  10. Felipe ContrerasApr 21, 2014
  11. [NOT_A_PATCH] A naive attempt to cross-build Linux->mingw64 GitMarat Radchenko, Apr 21, 2014
  12. Felipe ContrerasApr 21, 2014
  13. Felipe ContrerasApr 22, 2014
  14. Marat RadchenkoApr 22, 2014
  15. Felipe ContrerasApr 22, 2014
  16. Johannes SchindelinApr 22, 2014
  17. Johannes SchindelinApr 22, 2014
  18. David KastrupApr 22, 2014
  19. Felipe ContrerasApr 22, 2014
  20. Johannes SchindelinApr 22, 2014
  21. Sebastian SchuberthApr 19, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.