From: Graham Percival <graham@percival-music.ca>
Date: Wed, 17 Jun 2009 19:33:21 +0000 (-0700)
Subject: Doc: clarify process of git commits.
X-Git-Tag: release/2.13.2-0~20
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=6bd591e40918b70c396064be335bd03bc2f928cd;p=lilypond.git

Doc: clarify process of git commits.
---

diff --git a/Documentation/devel/git-starting.itexi b/Documentation/devel/git-starting.itexi
index 07f63a09e3..c50ba18da4 100644
--- a/Documentation/devel/git-starting.itexi
+++ b/Documentation/devel/git-starting.itexi
@@ -214,10 +214,18 @@ git format-patch origin
 The commit should include a brief message describing the change.
 This consists of a one-line summary describing the change, and
 if necessary a blank line followed by several lines giving the
-details.
+details:
 
-If the change is to the documentation only the one-line summary
-should be prefixed with "Docs: ".
+@example
+Did household chores.
+
+I hung up the wet laundry and then washed the car.  I also
+vacuumed the floors, rinsed the dirty dishes, fed the cat, and
+recalibrated the temporal flux machine.
+@end example
+
+If the change is to the documentation only then the one-line
+summary should be prefixed with @qq{Docs: }.
 
 If you added a file to the source code, you must add it to git
 with:
@@ -232,7 +240,8 @@ git add FILENAME
 These commands will produce one or more files named
 @file{0001-xyz}, @file{0002-abc}, etc. in the top directory of the
 git tree.  Send an email to @email{lilypond-devel@@gnu.org} with
-these files attached.
+these files attached, and a developer will review and apply the
+patches to the main repository.
 
 
 @node Committing directly