You got me on one part, I can take a pretty strong zealous position on this.

However, I didn't know about the git Windows support that you mentioned (#2 
that you mentioned).  Usually I worked in a unix environment and felt most 
comfortable there, so I became most familiar there.

Perhaps I'm clumsily venturing into this area, I mean no harm.

On Thursday, October 18, 2012 6:58:41 PM UTC-4, Konstantin Khomoutov wrote:
> On Thu, Oct 18, 2012 at 02:58:56PM -0700, Yves S. Garret wrote: 
> > Yes, but vetoed the idea.  For one I'm not a fan of Windows + Git 
> > "integration".  Second of all, I prefer to work from the command line. 
> Sorry for probably being harsh, but this sounds like a undereducated 
> religious bullshit.  Two facts to contradict your beleifs: 
> 1) Cygwin exactly provides integration of certain Unix tools with 
>    Windows.  I fail to see why it's okay for Cygwin but not for Git. 
> 2) Git for Windows (which Thomas called "msysgit") does really come 
>    packaged with the two standards GUI tools (git gui and gitk), 
>    and also provides a certain level of integration with Windows 
>    Explorer context menus (a tool called Git Cheetah; opt-in while 
>    installing) but their usage it not in any way enforced on you. 
>    There's even a "Git bash" application packaged, which is the bash 
>    shell.  You can use regular git command-line tools either from 
>    that Git bash of from the regular Windows shell (cmd.exe). 
> And no, I'm not suggesting to depart from using Cygwin: if you have use 
> for it outside working with Git, then it have perfect sense to try 
> having Git work there. 
> But for the majority of Windows users, having Git nicely integrated into 
> the system is probably preferable compared to installing Cygwin. 
> That's why Git for Windows exists. 
> Note that the ultimate goal for that project, as I understand it, is to 
> finally have its developments to be fully integrated upstream, so that 
> there's just one Git, cross-platform.  The relevant patches are already 
> and for the long time actively flowing upstream, but the merge is not 
> done yet. 

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To view this discussion on the web visit
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to