From: Heiko Voigt <hvoigt@hvoigt.net>
To: Marat Radchenko <marat@slonopotamus.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org,
msysGit Mailinglist <msysgit@googlegroups.com>
Subject: Re: Re: Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows
Date: Sat, 19 Apr 2014 21:24:09 +0200 [thread overview]
Message-ID: <20140419192409.GA8140@book-mint> (raw)
In-Reply-To: <20140419165832.GA23227@seldon>
On Sat, Apr 19, 2014 at 08:58:32PM +0400, Marat Radchenko wrote:
> On Sat, Apr 19, 2014 at 05:24:33PM +0200, Johannes Schindelin wrote:
> > Marat, please do not add to the confusion. "msysGit" is the name of the
> > *development environment* for developing Git for Windows.
>
> This confusion comes from the fact that major part of msysGit is packaged
> with Git for Windows to be used at runtime.
Only the tools that are needed to run git (and some that the
contributors like) are packaged in Git for Windows. For example there is
no compiler or similar packaged.
> If you insist on msysGit-is-a-development-environment, you have to admit
> that msysGit is technically a fork of msys.
Well it is a git repository that conveniently packages all the needed
tools you need to build "Git for Windows" together. It is a little bit
quick and dirty but it works. We have nothing against improving this
situation.
> My approach undoes this fork step and uses upstream runtime environment
> as-is, be it msys, msys2, Cygwin or even SUA [1]. I could even make it a
> noop and say "dear user, I don't care how, but please put sh/awk/find/etc
> on PATH to make Git work, like things normally happen in *nix world".
>
> Actually, even if Git was pure C, things like `git filter-branch` would
> be almost useless without coreutils & friends.
>
> > After all, there is no reason for yet another fork.
>
> If there wasn't, mingwGitDevEnv would not be started.
I would not consider mingwGitDevEnv a fork. It is more msysgit next
generation. But it needs more work to fully replace msysgit.
> I'd say I am doing a 'rebase' instead of 'fork' by using codebase of
> Git for Windows (upstream Git sources with Windows-specific patches)
> but replacing msysGit-provided runtime environment with another one.
The downside of doing this approach is that you regularly have to update
your 'rebase' and fix problems. If you integrate your changes into
msysgit itself you do not have to do that anymore.
Well, if it is one of your changes that breaks something, it still would
be nice if you do so ;-)
> [1]: http://en.wikipedia.org/wiki/Windows_Services_for_UNIX
Cheers Heiko
P.S.: BTW, just in case: Being criticized in open-source is good. Even
though it might not feel like that. It means people care about the stuff
you do and think it is important enough it deserves a reply. They just
want to help you improve it.
--
--
*** 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.
next prev parent reply other threads:[~2014-04-19 19:24 UTC|newest]
Thread overview: 16+ 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
2014-04-19 15:24 ` Johannes Schindelin
2014-04-19 16:58 ` Marat Radchenko
2014-04-19 19:24 ` Heiko Voigt [this message]
-- 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-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-22 13:14 ` Johannes Schindelin
2014-04-22 16:00 ` Felipe Contreras
2014-04-22 16:14 ` Johannes Schindelin
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=20140419192409.GA8140@book-mint \
--to=hvoigt@hvoigt.net \
--cc=Johannes.Schindelin@gmx.de \
--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).