[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: |
Mon, 22 Aug 2011 10:52:23 +0200 |
User-agent: |
KMail/1.13.6 (Linux/2.6.38-10-generic; KDE/4.7.0; i686; ; ) |
Am Monday, 22. August 2011, 09:49:41 schrieben Sie:
> Yes, definitely do the pushing stuff in a separate patch. But here's an
> outline:
> 1. update with
> git pull -r
> 2. check you only have 1 patch ready with
> git status
That's the step where I like qgit, because it gives you a really good
graphical overview over the commit tree, the changed files and the changes
itself. So I can review the exact changes once again.
And you also see immediately if you did a "git push" and inadvertedly created
a merge commit.
Cheers,
Reinhold
--
------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
* Financial & Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
- Re: DOC: Revise CG 3.4 Commit Access (issue 4898058), (continued)
- 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
- Re: DOC: Revise CG 3.4 Commit Access (issue 4898058), ColinPKCampbell, 2011/08/23