Git also changes the way that developers interact with the OpenAFS tree. Instead of just having a single version of the tree on your local machine, you have a compressed copy of the entire repository. Additionally, you no longer have to produce patches to send code upstream - any developer can push into the OpenAFS repository directly, through gerrit, our code review tool.
+* <a href="http://www.optimaweb.co.id/jasa-seo">Jasa SEO</a>
+* <a href="http://blogs.unpad.ac.id/dominodiaz/">Blog Kuliner</a>
+* <a href="http://adrian-fh98.web.unair.ac.id/">Adrian</a>
+
Whilst git is a far more powerful tool than CVS it is also, inevitably, more complex. This document can only scratch the surface of what's possible with git - there are many, many, documents available that describe git in greater detail, and references to some of them are provided at the end.
## <a name="Getting git"></a> Getting git
-Firstly, if your machine doesn't already have it installed, get a copy of the 'git' version control system. This is available for many platforms from their upstream package repositories or, failing that, can be downloaded in both source and binary form from <http://git-scm.com/download>
+Firstly, if your machine doesn't already have it installed, get a copy of the 'git' version control system. This is available for many platforms from their upstream package repositories or, failing that, can be downloaded in both source and binary form from
## <a name="Getting the _OpenAFS repository"></a> Getting the OpenAFS repository
git://git.openafs.org / openafs-wiki.git / blobdiff