From: Carl Sorensen <c_sorensen@byu.edu>
Date: Mon, 3 May 2010 04:19:27 +0000 (-0600)
Subject: Doc: Contributing -- add instructions on git-cl issue`
X-Git-Tag: release/2.13.20-1~9
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=cc26117eb87a75ba461861d7c890e7e46e751b65;p=lilypond.git

Doc: Contributing -- add instructions on git-cl issue`
---

diff --git a/Documentation/contributor/programming-work.itexi b/Documentation/contributor/programming-work.itexi
index e1557ad1ba..6e2153a26c 100644
--- a/Documentation/contributor/programming-work.itexi
+++ b/Documentation/contributor/programming-work.itexi
@@ -1360,6 +1360,20 @@ As revisions are made in response to comments, successive patch sets
 for the same issue can be uploaded by reissuing the git-cl command
 with the modified branch checked out.
 
+Sometimes in response to comments on revisions, the best way to
+work may require creation of a new branch in git.  In order to
+associate the new branch with an existing Reitveld issue,
+the following command can be used:
+
+@example
+git-cl issue issue-number
+@end example
+
+@noindent
+where @code{issue-number} is the number of the existing Rietveld
+issue.
+
+
 
 @node Push patch
 @subsection Push patch