(no commit message)

diff --git a/GitDevelopers.mdwn b/GitDevelopers.mdwn
index 0850032..f788f6c 100644 (file)
--- a/GitDevelopers.mdwn
+++ b/GitDevelopers.mdwn
@@ -1,5 +1,7 @@
 Git opens up a number of new options for contributing to OpenAFS. For the first time, it is easy to review code that is pending addition to the OpenAFS tree. In fact, reviewing code is one of the best ways to ensure that the releases that OpenAFS ships remain stable and functional. If you are interested purely in reviewing, then please skip to that section towards the end of this document.
-
+[Toko Bunga](http://www.tokobungasabana.com)
+[Jasa SEO](http://www.optimaweb.co.id/jasa-seo)
+[Blog Teknik](http://adrian-fh98.web.unair.ac.id/)
 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.
 
 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.