Why using git would be awesome for nexuiz

[parasti]

What most of you and I think of which is better is basically irrelevant anyway... A move to Git only makes sense if the main contributors are already familiar with Git and DVCS in general. SVN users trying to duplicate an SVN workflow treating Git as "almost like SVN, but with entire repo available locally" will inevitably be disappointed, because Git is fundamentally different from SVN and encourages an entirely different way of working.

[Alien]

I just added the fire to the flame. I don't think one is better or the other. The same way I don't prefer vi(m) to emacs or vice versus.

[Psychcf]

Actually, Mercurial is better than those two.

For comparison: http://better-scm.berlios.de/comparison/comparison.html
http://mail.python.org/pipermail/python ... 87931.html

Yeah, there are other version control systems like mercurial and bazaar, but git seems to be the most notable out of them.

I've watched linuses speech about GIT, yet, some things they claim (e.g. "much faster") is ... well, no surprise if git encourages you to use much smaller projects. I don't see how full nexuiz svn checkout would be much slower compared to a full git checkout of nexuiz. You need to download it from a host, there is bandwith that limits you, and no great tool won't come past that.

Apart from that I haven't quite understood yet how you can share your own repository when you are "just a user" behind a firewall. How does that work?

From what I've experienced, checking out a git repo with nexuiz in it takes less time then it does on SVN. I estimate that git takes about 1.6 hours, while SVN takes 2 or 3 hours.

As for the local repository thing, you can do something like this, and it works exactly as if you were using a remote repository (except you aren't pushing to anything):

Code: Select all

git init myrepo
cd myrepo
touch foo.txt
vim foo.txt
#editing
git add foo.txt
git commit -m "initial checkin"
vim foo.txt
#more editing
git add foo.txt
git commit -m "some random change to a file"

in that way, you have a local repo that you can later push to a remote server, if you wanted to.

The other cool thing about git is that you can check out an SVN repo as a git repository, and you'd be able to do local commits and such.

[parasti]

I didn't take note of the exact time, but for me a clone of nexuiz-classbased.git took about the same time as checking out trunk with SVN, which is about 1.5 hours. Fun fact: an SVN checkout of Nexuiz trunk is actually a bit larger than a git-svn clone of the entire history of trunk since 2003 + working tree: 3.2 GB vs 3.1 GB.

[C.Brutail]

I've moved the thread to development,as it's a more apropiate place for discussions like this imho.

[Psychcf]

I didn't take note of the exact time, but for me a clone of nexuiz-classbased.git took about the same time as checking out trunk with SVN, which is about 1.5 hours. Fun fact: an SVN checkout of Nexuiz trunk is actually a bit larger than a git-svn clone of the entire history of trunk since 2003 + working tree: 3.2 GB vs 3.1 GB.

Oh, maybe I was off b/c I was comparing it to the entire nexuiz SVN repo, as opposed to just trunk. Git does a good job of compressing the history though.

[some-guy]

Git FTW!
Some notable projects using git:
* Linux Kernel
* Freedesktop.org (mesa/x/libdrm)
* Perl
* Gnome
* Android
* Fedora
* Git

Git is imo much better than svn, you can 'easily' revert commits (git revert commitname), and also has many other advanced/rarely-used features. Branching is also much better.

[mand1nga]

[Alien]

http://whygitisbetterthanx.com/ and http://whyhgisbetterthanx.com/

[[-z-]]

http://whygitisbetterthanx.com/

n1, thanks (thanx) for that.