Doc: CG: add instructions for staging branch

Doc: CG: add instructions for staging branch

[Graham Percival, 2011-12-09 14:23:02]

this is the second draft of the patch that was formerly here:
http://codereview.appspot.com/5440080

[Graham Percival, 2011-12-09 14:31:47]

I should clarify: I'm going to move pretty quickly on this one.  As long as
these instructions aren't completely garbage, I'll push them to staging in 24
hours.

The rationale dates back to the original concept of the CG of being "basically
like a wiki" -- we don't want to lose info by getting bogged down in details. 
As long as the docs compile, this isn't going to negatively impact users or
other developers.

[PhilEHolmes, 2011-12-09 15:24:38]

Minor suggested change.  Otherwise LGTM.

http://codereview.appspot.com/5467051/diff/1/Documentation/contributor/source...
File Documentation/contributor/source-code.itexi (right):

http://codereview.appspot.com/5467051/diff/1/Documentation/contributor/source...
Documentation/contributor/source-code.itexi:1690: If you are working on
branches, then do:
Think you should say that the example branch in the code below is called pq; or
perhaps change "git merge pq" to "git merge my_branch_name".

[Carl, 2011-12-10 00:33:28]

One minor comment

http://codereview.appspot.com/5467051/diff/1/Documentation/contributor/source...
File Documentation/contributor/source-code.itexi (right):

http://codereview.appspot.com/5467051/diff/1/Documentation/contributor/source...
Documentation/contributor/source-code.itexi:156: The above command will put the
it in @file{~/lilypond}, where
~/lilypond-git, I think