(no commit message)

[openafs-wiki.git] / GitDevelopers.mdwn

diff --git a/GitDevelopers.mdwn b/GitDevelopers.mdwn
index 83fbc43..60753b9 100644 (file)
--- a/GitDevelopers.mdwn
+++ b/GitDevelopers.mdwn
@@ -1,4 +1,4 @@
-# <a name="Git and gerrit for developers"></a> Git and gerrit for developers
+# <a href="http://www.tokobungasabana.com">Toko Bunga</a> gift for developers
 
 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.
 
@@ -228,6 +228,7 @@ Secondly, each commit should have a meaningful revision log. The internals of gi
 
 Thirdly, each commit should have a valid changeID. Manually maintaining these is difficult and error prone, so we would strong advise that you install the changeID hook detailed earlier. This will automatically add a [[ChangeId]] line to your commit message if it doesn't already contain one.
 
+
 Fourthly, each commit must adhere to the OpenAFS whitespace policy whereby new commits will not be accepted if they have trailing spaces, spaces before tabs, or indentation without tabs.  Git can be configured to highlight the whitespace policy violation with the following global setting:
 
     git config --global core.whitespace trailing-space,space-before-tab,indent-with-non-tab