CG: explain how to add git-cl to PATH

[lilypond.git] / Documentation / contributor / source-code.itexi

diff --git a/Documentation/contributor/source-code.itexi b/Documentation/contributor/source-code.itexi
index de292c99f6d851cdbc763adf1819e006726e8bdc..ea8fc8775c59007ed7831b1b3c07260edc1e9887 100644 (file)
--- a/Documentation/contributor/source-code.itexi
+++ b/Documentation/contributor/source-code.itexi
@@ -913,10 +913,18 @@ git clone git://github.com/gperciva/git-cl.git
 @end example
 
 @item
-Add the @file{git-cl/} directory to your PATH, or create a
-symbolic link to the @command{git-cl} and @command{upload.py}
-scripts in one of your PATH directories (such as
-@file{$HOME/bin}).
+Add the @file{git-cl/} directory to your PATH,
+or create a symbolic link to the @command{git-cl}
+and @command{upload.py} scripts in one of your PATH
+directories (such as @file{$HOME/bin}).
+
+In Ubuntu (and Lilydev), you can add directories to PATH
+by adding this line to a hidden file @file{.bashrc},
+located in your home directory:
+
+@example
+PATH=~/type-here-directory-containing-git-cl:"$@{PATH@}"
+@end example
 
 @end enumerate
 
@@ -1681,10 +1689,16 @@ do:
 git checkout staging
 git pull -r
 git am 0001-my-patch.patch
+gitk
 git push origin staging
 git checkout master
 @end example
 
+@warning{Do not skip the @command{gitk} step; a quick 5-second
+check of the visual history can save a great deal of frustration
+later on.  You should only see that @command{staging} is only 1
+commit ahead of @code{origin/staging}.}
+
 @subsubheading If your work is in a branch
 
 If you are working on branches and your work in is
@@ -1694,9 +1708,15 @@ If you are working on branches and your work in is
 git checkout staging
 git pull -r
 git merge my_branch_name
+gitk
 git push origin staging
 @end example
 
+@warning{Do not skip the @command{gitk} step; a quick 5-second
+check of the visual history can save a great deal of frustration
+later on.  You should see that @code{staging} is only ahead of
+@code{origin/staging} by the commits from your branch.}
+
 
 
 @node Git on Windows