GIT instead of SVN

[xeross]

Hey Folks,

There's been recent suggestions that we should start using subversion to aid the people that modify the source so that they can easily update to the new code.

However subversion isn't that great really, it has something that's called race-conditions, meaning if 2 people commit at the same time it will mess up the entire source. and there's no way to revert something except by manually reversing and then commiting.

Additionally, you can't really branch well with it, and merging stuff is extremely hard.

So what I'm suggesting is instead of subversion we use git.

First of all it's decentralized, meaning everyone has the entire repository on their pc when they check the repository out, this makes it easy to create own branches and mess with it, plus it's a lot faster because it doesn't have to poll a remote server for changelogs, revisions etc.

The only problem is that it's a bit harder to learn how to use it compared to SVN, however there's TortoiseGIT which is basically TortoiseSVN for git, and some git GUIs are available.

For more reading check http://en.wikipedia.org/wiki/Git_%28software%29

Tell me what you think.

Regards, Xeross

[perikles184]

I like the idea of subversion, and it does definitely come in handy when you have very few people working on a project, but you're right of the 'race-conditions'. Could have _dire_ consequences!

I like TortoiseSVN…

[Rithy58]

Use SVN but only some people have permission to commit.

If we have 100 user that have write permission, we're not gonna commit at the same time.
We can even maybe make schedule. And everyone else have only read permission.
I don't even think we have 100 people that can code really good.

Cause…think about it. If we let everyone write, the source WILL be messed up.

Sincerely,
Rithy

[xeross]

We could use GIT and host it on something like github, that way people can create their own branches and stuff. and even if we only have a few people working on it that would eliminate race conditions, but still decentralized would be a lot better.

Regards, Xeross

[Matilda]

I really really don't like GIT.

[xeross]

@Matilda:

> I really really don't like GIT.

Why

Regards, Xeross

[Mellowz]

Eclipse already uses an SVN server, but it's not public.


I want to make it public (read access), but I keep forgetting to talk to Marsh about it.

I've used them both, and SVN comes out on top.

However, if we make the SVN public, it will defeat the purpose of releases as everyone will just download the latest working revision.

[xeross]

You ment you've used SVN and GIT ? and SVN came out on top, hmm, seems like you chose SVN because it's a lot easier. well hope it gets public soon, and I'll create a GIT repo from the SVN.

There will still be a use for releases: for people that don't know how to use SVN, for stable releases instead of potentially unstable trunk.

Regards, Xeross

[Mellowz]

@Xeross:

> You ment you've used SVN and GIT ? and SVN came out on top, hmm, seems like you chose SVN because it's a lot easier. well hope it gets public soon, and I'll create a GIT repo from the SVN.
>
> There will still be a use for releases: for people that don't know how to use SVN, for stable releases instead of potentially unstable trunk.
>
> Regards, Xeross

GIT and SVN have just about identical functions which are done in the same exact way.

People who contribute would call them "revisions" and not releases.

[xeross]

I am talking about releases as in well kind of tags/branches or just zips of a certain release.
And if you claim GIT and SVN are about identical all I can say is you're completely wrong.

Regards, Xeross

[Mellowz]

The basic commands of SVN and GIT are all that I need to develop and application online.

I use commit, log view, and sometimes patches, and that's it.

You don't need all those other features to develop Eclipse.

Why change to GIT when SVN works just fine for the type of development Eclipse requires.

Sort of like, "If it isn't broken, why fix it?"

[xeross]

@Mellowz:

> The basic commands of SVN and GIT are all that I need to develop and application online.
>
> I use commit, log view, and sometimes patches, and that's it.
>
> You don't need all those other features to develop Eclipse.
>
> Why change to GIT when SVN works just fine for the type of development Eclipse requires.
>
> Sort of like, "If it isn't broken, why fix it?"

Well the problem with SVN is that it's all remote so for a log, revert, or any operation it needs to query the remove server, with GIT all is stored on the local PC saving bandwidth and it's a lot faster. It also has built in branching etc. where you use folders with subversion.

Regards, Xeross

[Mellowz]

@Xeross:

> Well the problem with SVN is that it's all remote so for a log, revert, or any operation it needs to query the remove server, with GIT all is stored on the local PC saving bandwidth and it's a lot faster. It also has built in branching etc. where you use folders with subversion.
>
> Regards, Xeross

It's fast on POSIX-based OS's, but as developer I really don't see these as reasons for switching over.

[xeross]

I have GIT on my windows box and it's maybe slower then on any linux distro, but it's still dozens of times faster then SVN.

Another reason to switch is branching. someone could make let's say a custom inventory system. with SVN you would need to use patch files, and if you use multiple edits the patch may fail. with git you can merge one branch into another and if there are any conflicts it can be easily solved using something like Beyond Compare.

Regards, Xeross