From cc26117eb87a75ba461861d7c890e7e46e751b65 Mon Sep 17 00:00:00 2001 From: Carl Sorensen <c_sorensen@byu.edu> Date: Sun, 2 May 2010 22:19:27 -0600 Subject: [PATCH] Doc: Contributing -- add instructions on git-cl issue` --- Documentation/contributor/programming-work.itexi | 14 ++++++++++++++ 1 file changed, 14 insertions(+) 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 -- 2.39.5