On Mon, Feb 14, 2011 at 11:13 PM, Max Rydahl Andersen <max.andersen@redhat.com> wrote:

> My main contras for Git:
>       • It is poorly integrated with Windows and Eclipse.

For Windows - is that really still the case ?
It is built on Perl and does not work without MinGW. It is just a matter of taste, but for me it feels like a Linux emulator.
Last I tried it seemed to work fine ?
I used this http://help.github.com/win-git-installation/

You had any specific bad experiences ?
As I remember, when I tried it (~1 year ago), it had a very unstable support of git svn. As I said, after a lot of attempts I was unable to create a Git mirror.

About Eclipse, egit seem to be doing well ?
note, since git is darn fast I rarely eclipse tooling worth bothering with it...but again
I'll need to try on some more real examples to tell (hence my attempt on getting a real git repo to work with)

>       • Git repo will be too big. Thus this is a question for me will be commits faster or not. It will big because:
>               • JBoss Tools SVN consists of pretty coupled projects, so we have(?) to create a single Git repo for all of them.

well, its always been the intent these should get decoupled more and more with proper API's...one of the reasons that haven't happen
could be "blamed" on the fact the source is kept so close so its easy to "cheat" instead of defining proper API's.

>               • There are a lot of binaries (jars, images, videos, giant zip-files, ...). If we want to have all SVN history in Git, we have to add all these binaries to the mirror. I expect it will take approx 5GB (SVN repo itself takes 7GB now).

hmm - what repo are you using ? My repo with most projects built is a total of 3.7GB ...thus its (hopefully) much less since most are not versioned data.
I have a local SVN mirror. Its size is 7GB.

We haven't had videos in the main repo for years and they were seldom changed thus shouldn't be too much - but we'll see.

btw. jars is often something that can be fixed - again, being sloppy about adding many big jars for testing a basic feature often is not needed.
I mean we cannot remove jars from the history. There are only two ways: or create a new Git repo from scratch, or accept that it will be huge.

> Anyway, Max, if you succeed with creation of the mirror, please share it. I would like to play with it too :) I tried to create a Git mirror some time ago, but after a lot of attempts I decided that it is not possible on Windows without direct access to the SVN repo.

yup - i've created a local svn mirror and it is currenty running svn2git to get a full repo to see how bad/big the damage is.

The final version i'll probably just include all the later branches/tags instead of the full story.

/max