Re: Git for Windows 1.6.2.1-preview20090322

[Johannes Schindelin <Johannes.Schindelin@gmx.de>]

Hi,

On Tue, 24 Mar 2009, Markus Heidelberg wrote:

> the company I'm working for plans to switch from our current commercial 
> VCS, now I have the job to compare different tools (svn, git). Our 
> clients run on Windows and probably our offices in foreign countries 
> should work on our repository, too.

This...

> Johannes Schindelin, 22.03.2009:
> > Disclaimer: Git for Windows is still in a state where I do _not_ 
> > recommend using it unless you have the means to fix issues.  Unlike 
> > the git.git developer community, the msysGit team is heavily 
> > undermanned.

... and this make me believe that Git for Windows is not at all what you 
want.  You seem to want to purely _use_ Git, and at this time, it is just 
not there.

It would be different if you/your company were willing to pay for support, 
but I just do not see from your mail that you are willing to contribute to 
Git for Windows.

> > - If you want to specify a different location for --upload-pack, you 
> >   have to start the absolute path with two slashes. Otherwise MSys 
> >   will mangle the path.
> 
> Only for msysgit on the server side, right? Then, never mind.

Nope.  There is no msysgit on the server side.  So no, it applies to the 
client side.

> > - git and bash have serious problems with non-ASCII file names (Issue 
> >   80, 108, 149, 159, 188).
> 
> This may be a problem.

Indeed.  I mean, 5 issues, and none of them resolved.

> > - If configured to use plink, you will have to connect with putty 
> >   first, as you cannot accept the host key due to the console window 
> >   being blocked (Issue 96).
> 
> Just use OpenSSH?
> Problem in GUIs or only CLI?

See the issue if you want to know more.

> > - There are a few issues with ssh hanging (Issue 197), permission 
> >   denied on renaming pack files (mentioned in Issue 194), and spurious 
> >   write errors during rebase (Issue 200) that seem not to be 
> >   reproducible on most computers.
> 
> OK, strange and not reproducible errors are a little bit scary.

A little scary?  No.  _Very_ scary.

Especially since the involved parties either do not have the time or the 
willingness to investigate in detail.

As these issues are not reproducible on my side, it also does not make me 
think more highly of that particular Operating System.

> I suppose there are already people using msysgit productive at work, are 
> these only people who know how to fix such problems?

Yes.

> Regardless of git's Windows problems, another problem will probably be 
> finding a decent GUI that suits my colleagues.

Yes.

Ciao,
Dscho