Merge branch 'maint'

diff --git a/Documentation/howto/maintain-git.txt b/Documentation/howto/maintain-git.txt
index d90230726489b4600a624e166f3c0c46bc65a102..33ae69c11f0f70b6dd1881f0ae013eca653acf5c 100644 (file)
--- a/Documentation/howto/maintain-git.txt
+++ b/Documentation/howto/maintain-git.txt
@@ -1,15 +1,19 @@
 From: Junio C Hamano <gitster@pobox.com>
 Date: Wed, 21 Nov 2007 16:32:55 -0800
 Subject: Addendum to "MaintNotes"
-Abstract: Imagine that git development is racing along as usual, when our friendly
+Abstract: Imagine that Git development is racing along as usual, when our friendly
  neighborhood maintainer is struck down by a wayward bus. Out of the
  hordes of suckers (loyal developers), you have been tricked (chosen) to
  step up as the new maintainer. This howto will show you "how to" do it.
+Content-type: text/asciidoc
+
+How to maintain Git
+===================
 
 Activities
 ----------
 
-The maintainer's git time is spent on three activities.
+The maintainer's Git time is spent on three activities.
 
  - Communication (45%)
 
@@ -86,7 +90,7 @@ this mailing list after each feature release is made.
 A Typical Git Day
 -----------------
 
-A typical git day for the maintainer implements the above policy
+A typical Git day for the maintainer implements the above policy
 by doing the following:
 
  - Scan mailing list.  Respond with review comments, suggestions
@@ -210,8 +214,8 @@ by doing the following:
    The result is a script that lists topics to be merged in order to
    rebuild 'pu' as the input to Meta/Reintegrate script.  Remove
    later topics that should not be in 'jch' yet.  Add a line that
-   consists of '###' before the name of the first topic in the output
-   that should be in 'jch' but not in 'next' yet.
+   consists of '### match next' before the name of the first topic
+   in the output that should be in 'jch' but not in 'next' yet.
 
  - Now we are ready to start merging topics to 'next'.  For each
    branch whose tip is not merged to 'next', one of three things can
@@ -233,7 +237,8 @@ by doing the following:
      $ Meta/redo-jch.sh -c1
 
    to rebuild the 'jch' branch from scratch.  "-c1" tells the script
-   to stop merging at the '###' line you added earlier.
+   to stop merging at the first line that begins with '###'
+   (i.e. the "### match next" line you added earlier).
 
    At this point, build-test the result.  It may reveal semantic
    conflicts (e.g. a topic renamed a variable, another added a new
@@ -261,8 +266,8 @@ by doing the following:
      $ sh Meta/redo-jch.sh -u
 
    This removes topics listed in the script that have already been
-   merged to 'master'.  This unfortunately loses the "###" marker,
-   so add it again to the appropriate place.
+   merged to 'master'.  This may lose '### match next' marker;
+   add it again to the appropriate place when it happens.
 
  - Rebuild 'pu'.