Comments on: Gitting Started with Git – Quick and Dirty

By: Frank Arnold

Frank Arnold — Fri, 16 Oct 2009 16:03:22 +0000

Yes, its sometimes a bit overhead to have a repository (with Git a bare repository) and a working copy (which is at the same time the web-root). I think this comes a bit from the knowledge of other VCS systems like SVN which needs a central repository. But distributed version control systems doesn’t need a central repository.

For me the master branch is every time the main branch and so also the “live” branch. Testing and other things are done on additional branches which can be later merged with the master.
This easy handling with branches is the big advantage over SVN. “SVN has not a internal concept of a branch, only copies”.

By: Kevin Lloyd

Kevin Lloyd — Sun, 10 May 2009 19:47:36 +0000

The info is much appreciated Mr. Chris. I know Git is Linux (Unix) based (hence the interesting Windows Port). I was talking about the original install. When I Google “Windows git” or “OS X git” the first result is the installer page and you’re off and running with basic tools like “gitk” and “git gui” (which are all you really need, if you ask me).

The general problem I have with Linux is the lack of Documentation (oh, I’m going to get some pressure for this comment ) or the hidden nature of it. It is often assumed that Linux users already know mots of what they need.

The Ubuntu guide that I did find would suggest that Git would be included in the repository for Debian (and I’m assuming you can also Yum it for Fedora). I just didn’t include those, because I personally have not yet done these myself.

By: Chris

Chris — Sat, 09 May 2009 23:13:55 +0000

Not so fast about Linux users and git: Since Linus Torvalds originally wrote git for the Linux kernel and git is primarily developed on Linux then there is in fact tons and tons of git tools available for Linux. In fact, the windows and mac software are merely ports of the original Linux tools. All major distros (and probably all minor distros for that matter) come with git tools available. For example, in Fedora 10 we have the following git tools available to install directly from the standard repos… there is no need to build from source:

git.x86_64 : Core git tools
git-all.x86_64 : Meta-package to pull in all git tools
git-arch.x86_64 : Git tools for importing Arch repositories
git-cola.noarch : A highly caffeinated git gui
git-cpan-patch.noarch : Patch CPAN modules using Git
git-cvs.x86_64 : Git tools for importing CVS repositories
git-daemon.x86_64 : Git protocol dæmon
git-email.x86_64 : Git tools for sending email
git-gui.x86_64 : Git GUI tool
git-svn.x86_64 : Git tools for importing Subversion repositories
gitk.x86_64 : Git revision tree visualiser
gitosis.noarch : Git repository hosting application
gitweb.x86_64 : Simple web interface to git repositories

Anyway, nice intro, I keep wondering whether it’s worth moving from SVN but can’t really see that the advantages yet outweigh the cost of learning and setting up a new system. It’s always good to read other people’s experiences though.

Chris’s last blog post..How-To: Automated incremental daily backups to Amazon S3 using Duplicity