git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Voigt <hvoigt@hvoigt.net>
To: marat@slonopotamus.org
Cc: git@vger.kernel.org, msysGit Mailinglist <msysgit@googlegroups.com>
Subject: Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows
Date: Sat, 19 Apr 2014 08:31:34 +0200	[thread overview]
Message-ID: <20140419063133.GA3617@book-mint> (raw)
In-Reply-To: <20140403131850.GA24449@seldon>

Hi Marat,

On Thu, Apr 03, 2014 at 05:18:50PM +0400, marat@slonopotamus.org wrote:
> I'm proud to announce WinGit:
> an attempt to bring Git powers to 64-bit Windows.

So the reason for this new package is that you need 64bit binaries?

> Relationship with msysgit
> =========================
> 
> Unlike msysgit, WinGit is a pure-Windows binary build with MSVC.
> 
> Like msysgit, WinGit also uses msys environment (sh/perl/etc) both during
> build-time and runtime.

I can see the need for a pure Windows solution (no msys tools at least for
runtime). But this sounds to me that the only thing you changed is the
compiler and 64bit? The git binaries in msysgit are already pure Windows
binaries with no need of msys.dll. The only reason why so many other
tools are shipped with msysgit is to run scripted commands (e.g. like
gitk or rebase).

What is the reason of using a closed source compiler? Why not use the
64bit mingw that is already used to build the 64bit explorer extension
to package 64bit binaries along with the 32bit ones in the installer?

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? I think the main reason why there are no 64 bit binaries shipped
with msysgit is that nobody needed them and the need to ship both (at
least for some time).

That would also make the maintenance burden easier for you.

Cheers Heiko

-- 
-- 
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.

You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en

--- 
You received this message because you are subscribed to the Google Groups "msysGit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  parent reply	other threads:[~2014-04-19  6:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03 13:18 [ANNOUNCE] WinGit - native x86/x64 Git for Windows marat
2014-04-03 13:48 ` Konstantin Khomoutov
2014-04-03 14:07   ` Marat Radchenko
     [not found] ` <CAAH6HY8DbQCMJhb4fY3-aLbriUHOS4zeizHjPy+FMmxuyHQxxQ@mail.gmail.com>
2014-04-03 15:03   ` Fwd: " Vincent van Ravesteijn
2014-04-09 17:27 ` Felipe Contreras
2014-04-19  6:31 ` Heiko Voigt [this message]
2014-04-19 15:24   ` Johannes Schindelin
2014-04-19 16:58     ` Marat Radchenko
2014-04-19 19:24       ` Heiko Voigt
  -- strict thread matches above, loose matches on Subject: below --
2014-04-19 13:35 Marat Radchenko
2014-04-19 18:42 ` Heiko Voigt
2014-04-20 22:10   ` [msysGit] " 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-22 13:14           ` Johannes Schindelin
2014-04-22 14:17             ` David Kastrup
2014-04-19 20:56 ` Sebastian Schuberth

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=20140419063133.GA3617@book-mint \
    --to=hvoigt@hvoigt.net \
    --cc=git@vger.kernel.org \
    --cc=marat@slonopotamus.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).