[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: DOC: Revise CG 3.4 Commit Access (issue 4898058)
From: |
reinhold . kainhofer |
Subject: |
Re: DOC: Revise CG 3.4 Commit Access (issue 4898058) |
Date: |
Thu, 18 Aug 2011 11:42:06 +0000 |
On 2011/08/18 11:21:22, PhilEHolmes wrote:
LGTM too. My suggestion would be to add some instructions about
actually
pushing. It took me a while to convince myself that all that appears
to be
needed is to have an unpushed commit and type "git push".
Yes, it' s really that simple ;-)
We should add the advice, though, to do a "git pull -r" immediately
before (to get the latest changes from the server), because otherwise
the "git push" might fail if someone else has pushed something to master
meanwhile.
http://codereview.appspot.com/4898058/
- DOC: Revise CG 3.4 Commit Access (issue 4898058), percival . music . ca, 2011/08/17
- Re: DOC: Revise CG 3.4 Commit Access (issue 4898058), ColinPKCampbell, 2011/08/18
- Re: DOC: Revise CG 3.4 Commit Access (issue 4898058), janek . lilypond, 2011/08/21
- Re: DOC: Revise CG 3.4 Commit Access (issue 4898058), ColinPKCampbell, 2011/08/21
- Re: DOC: Revise CG 3.4 Commit Access (issue 4898058), percival . music . ca, 2011/08/22