Re: [Fwd: Re: What's in git.git]

[Robin Rosenberg <robin.rosenberg.lists@dewire.com>]

söndag 19 november 2006 18:49 skrev Petr Baudis:
> On Sun, Nov 19, 2006 at 06:40:06PM CET, Jon Smirl wrote:
> > Brendan told me that he would not consider Mozilla moving to git until
> > a native Windows version is released so I just dropped the whole
> > thing. It is too much effort and they don't even really want it. They
> > are probably going to switch to SVN.  I told him that SVN would end up
> > being a disaster and he got mad at me. That's when I stopped working
> > on cvs2svn/git.
>
> I see. :-(
>
> Could you please publish cvs2git in whatever state you have it so that
> someone else possibly interested could pick it up and finish the missing
> bits? It would be shame if the already done work would end up wasted.
>
> > #2) git needs native Windows support, this probably includes MSVC
> > integration. There are a lot of non-technical people working on
> > Mozilla like accessibility, doc, artwork, translations, they are all
> > on Windows. Brendan explicitly ruled out cygwIn.
>
> This is sort of catch-22, we have probably no developers interested
> enough in porting Git to native Windows and it's not clear we are going
> to get any until Git runs on native Windows.

Having a usable set of git in C-format (or C++) is what it takes to get things 
rolling. Make the shores of Git-land shallow with nice beaches, so it easy to 
enter and you'll get people there, just out of curiosity. They'll start 
improving things after a while.

Even if it is possible to run bash, python, perl and who-knows-what in native 
windows it makes installing and packaging complicated. It is quite simple to 
install git under cygwin for people versed in cygwin or Linux, but not for 
those that have no interest in those two.

As for plugins to visual studio and othe strange things, they will come if a 
practically usable core set is in place, that can be built and redestributed 
without a ton of dependencies. People have used visual studio with CVS and 
other tools without plugins for a long time just fine so Git will do fine 
withour it for a while too. Eventually we'll have TortoiseGit. They key is a 
usable subset of Git that only requires a C compiler (or C++). Other 
solutions are ofcourse possible (like a C# re-implementation), but making 
things native C-code is the most straightforward path that doesn't split the 
code base.