War on whitespace

This uses "git-apply --whitespace=strip" to fix whitespace errors that have
crept in to our source files over time.  There are a few files that need
to have trailing whitespaces (most notably, test vectors).  The results
still passes the test, and build result in Documentation/ area is unchanged.

Signed-off-by: Junio C Hamano <gitster@pobox.com>

Documentation/RelNotes-1.5.0.4.txt

@@ -20,5 +20,3 @@ Fixes since v1.5.0.3
 * Documentation updates
 
 * User manual updates
-
-

Documentation/RelNotes-1.5.0.5.txt

@@ -24,5 +24,3 @@ Fixes since v1.5.0.3
 * Documentation updates
 
 * User manual updates
-
-

Documentation/RelNotes-1.5.0.6.txt

@@ -19,4 +19,3 @@ Fixes since v1.5.0.5
   - user-manual has better cross references.
 
   - gitweb installation/deployment procedure is now documented.
-

Documentation/RelNotes-1.5.1.3.txt

@@ -43,4 +43,3 @@ Fixes since v1.5.1.2
     description was given by the caller.
 
 Also contains various documentation updates.
-

Documentation/SubmittingPatches

@@ -296,15 +296,15 @@ diff --git a/pico/pico.c b/pico/pico.c
 --- a/pico/pico.c
 +++ b/pico/pico.c
 @@ -219,7 +219,9 @@ PICO *pm;
- 	    switch(pico_all_done){	/* prepare for/handle final events */
+	    switch(pico_all_done){	/* prepare for/handle final events */
- 	      case COMP_EXIT :		/* already confirmed */
+	      case COMP_EXIT :		/* already confirmed */
- 		packheader();
+		packheader();
 +#if 0
- 		stripwhitespace();
+		stripwhitespace();
 +#endif
- 		c |= COMP_EXIT;
+		c |= COMP_EXIT;
- 		break;
+		break;
- 
+
 
 (Daniel Barkalow)
 

Documentation/asciidoc.conf

@@ -54,5 +54,3 @@ ifdef::backend-xhtml11[]
 [gitlink-inlinemacro]
 <a href="{target}.html">{target}{0?({0})}</a>
 endif::backend-xhtml11[]
-
-

Documentation/config.txt

@@ -682,5 +682,3 @@ receive.denyNonFastForwards::
 transfer.unpackLimit::
 	When `fetch.unpackLimit` or `receive.unpackLimit` are
 	not set, the value of this variable is used instead.
-
-

Documentation/core-tutorial.txt

@@ -9,11 +9,11 @@ repository, mainly because being hands-on and using explicit examples is
 often the best way of explaining what is going on.
 
 In normal life, most people wouldn't use the "core" git programs
-directly, but rather script around them to make them more palatable. 
+directly, but rather script around them to make them more palatable.
 Understanding the core git stuff may help some people get those scripts
 done, though, and it may also be instructive in helping people
 understand what it is that the higher-level helper scripts are actually
-doing. 
+doing.
 
 The core git is often called "plumbing", with the prettier user
 interfaces on top of it called "porcelain". You may not want to use the
@@ -41,7 +41,7 @@ Creating a new git repository couldn't be easier: all git repositories start
 out empty, and the only thing you need to do is find yourself a
 subdirectory that you want to use as a working tree - either an empty
 one for a totally new project, or an existing working tree that you want
-to import into git. 
+to import into git.
 
 For our first example, we're going to start a totally new repository from
 scratch, with no pre-existing files, and we'll call it `git-tutorial`.
@@ -169,7 +169,7 @@ $ ls .git/objects/??/*
 and see two files:
 
 ----------------
-.git/objects/55/7db03de997c86a4a028e1ebd3a1ceb225be238 
+.git/objects/55/7db03de997c86a4a028e1ebd3a1ceb225be238
 .git/objects/f2/4c74a2e500f5ee1332c86b94199f52b1d1d962
 ----------------
 
@@ -220,7 +220,7 @@ you have not actually really "checked in" your files into git so far,
 you've only *told* git about them.
 
 However, since git knows about them, you can now start using some of the
-most basic git commands to manipulate the files or look at their status. 
+most basic git commands to manipulate the files or look at their status.
 
 In particular, let's not even check in the two files into git yet, we'll
 start off by adding another line to `hello` first:
@@ -350,7 +350,7 @@ Making a change
 
 Remember how we did the `git-update-index` on file `hello` and then we
 changed `hello` afterward, and could compare the new state of `hello` with the
-state we saved in the index file? 
+state we saved in the index file?
 
 Further, remember how I said that `git-write-tree` writes the contents
 of the *index* file to the tree, and thus what we just committed was in
@@ -370,7 +370,7 @@ file and the working tree, `git-diff-index` shows the differences
 between a committed *tree* and either the index file or the working
 tree. In other words, `git-diff-index` wants a tree to be diffed
 against, and before we did the commit, we couldn't do that, because we
-didn't have anything to diff against. 
+didn't have anything to diff against.
 
 But now we can do
 
@@ -379,7 +379,7 @@ $ git-diff-index -p HEAD
 ----------------
 
 (where `-p` has the same meaning as it did in `git-diff-files`), and it
-will show us the same difference, but for a totally different reason. 
+will show us the same difference, but for a totally different reason.
 Now we're comparing the working tree not against the index file,
 but against the tree we just wrote. It just so happens that those two
 are obviously the same, so we get the same result.
@@ -398,7 +398,7 @@ working tree, but when given the `\--cached` flag, it is told to
 instead compare against just the index cache contents, and ignore the
 current working tree state entirely. Since we just wrote the index
 file to HEAD, doing `git-diff-index \--cached -p HEAD` should thus return
-an empty set of differences, and that's exactly what it does. 
+an empty set of differences, and that's exactly what it does.
 
 [NOTE]
 ================
@@ -549,7 +549,7 @@ $ git-whatchanged -p --root
 ----------------
 
 and you will see exactly what has changed in the repository over its
-short history. 
+short history.
 
 [NOTE]
 The `\--root` flag is a flag to `git-diff-tree` to tell it to
@@ -637,7 +637,7 @@ So the mental model of "the git information is always tied directly to
 the working tree that it describes" may not be technically 100%
 accurate, but it's a good model for all normal use.
 
-This has two implications: 
+This has two implications:
 
  - if you grow bored with the tutorial repository you created (or you've
    made a mistake and want to start all over), you can just do simple
@@ -705,7 +705,7 @@ Many (most?) public remote repositories will not contain any of
 the checked out files or even an index file, and will *only* contain the
 actual core git files. Such a repository usually doesn't even have the
 `.git` subdirectory, but has all the git files directly in the
-repository. 
+repository.
 
 To create your own local live copy of such a "raw" git repository, you'd
 first create your own subdirectory for the project, and then copy the
@@ -718,7 +718,7 @@ $ cd my-git
 $ rsync -rL rsync://rsync.kernel.org/pub/scm/git/git.git/ .git
 ----------------
 
-followed by 
+followed by
 
 ----------------
 $ git-read-tree HEAD
@@ -738,7 +738,7 @@ up-to-date (so that you don't have to refresh it afterward), and the
 `-a` flag means "check out all files" (if you have a stale copy or an
 older version of a checked out tree you may also need to add the `-f`
 flag first, to tell git-checkout-index to *force* overwriting of any old
-files). 
+files).
 
 Again, this can all be simplified with
 
@@ -751,7 +751,7 @@ $ git checkout
 which will end up doing all of the above for you.
 
 You have now successfully copied somebody else's (mine) remote
-repository, and checked it out. 
+repository, and checked it out.
 
 
 Creating a new branch
@@ -760,14 +760,14 @@ Creating a new branch
 Branches in git are really nothing more than pointers into the git
 object database from within the `.git/refs/` subdirectory, and as we
 already discussed, the `HEAD` branch is nothing but a symlink to one of
-these object pointers. 
+these object pointers.
 
 You can at any time create a new branch by just picking an arbitrary
 point in the project history, and just writing the SHA1 name of that
 object into a file under `.git/refs/heads/`. You can use any filename you
 want (and indeed, subdirectories), but the convention is that the
 "normal" branch is called `master`. That's just a convention, though,
-and nothing enforces it. 
+and nothing enforces it.
 
 To show that as an example, let's go back to the git-tutorial repository we
 used earlier, and create a branch in it. You do that by simply just
@@ -778,7 +778,7 @@ $ git checkout -b mybranch
 ------------
 
 will create a new branch based at the current `HEAD` position, and switch
-to it. 
+to it.
 
 [NOTE]
 ================================================
@@ -825,7 +825,7 @@ checking it out and switching to it. If so, just use the command
 $ git branch <branchname> [startingpoint]
 ------------
 
-which will simply _create_ the branch, but will not do anything further. 
+which will simply _create_ the branch, but will not do anything further.
 You can then later -- once you decide that you want to actually develop
 on that branch -- switch to that branch with a regular `git checkout`
 with the branchname as the argument.
@@ -884,7 +884,7 @@ $ gitk --all
 will show you graphically both of your branches (that's what the `\--all`
 means: normally it will just show you your current `HEAD`) and their
 histories. You can also see exactly how they came to be from a common
-source. 
+source.
 
 Anyway, let's exit `gitk` (`^Q` or the File menu), and decide that we want
 to merge the work we did on the `mybranch` branch into the `master`
@@ -905,8 +905,8 @@ of it as it can automatically (which in this case is just merge the `example`
 file, which had no differences in the `mybranch` branch), and say:
 
 ----------------
-	Auto-merging hello 
+	Auto-merging hello
-	CONFLICT (content): Merge conflict in hello 
+	CONFLICT (content): Merge conflict in hello
 	Automatic merge failed; fix up by hand
 ----------------
 
@@ -1387,7 +1387,7 @@ repository. Kernel.org mirror network takes care of the
 propagation to other publicly visible machines:
 
 ------------
-$ git push master.kernel.org:/pub/scm/git/git.git/ 
+$ git push master.kernel.org:/pub/scm/git/git.git/
 ------------
 
 

Documentation/diff-format.txt

@@ -1,7 +1,7 @@
 The output format from "git-diff-index", "git-diff-tree" and
 "git-diff-files" are very similar.
 
-These commands all compare two sets of things; what is 
+These commands all compare two sets of things; what is
 compared differs:
 
 git-diff-index <tree-ish>::
@@ -139,28 +139,28 @@ index fabadb8,cc95eb0..4866510
 --- a/describe.c
 +++ b/describe.c
 @@@ -98,20 -98,12 +98,20 @@@
-  	return (a_date > b_date) ? -1 : (a_date == b_date) ? 0 : 1;
+	return (a_date > b_date) ? -1 : (a_date == b_date) ? 0 : 1;
   }
-  
+
 - static void describe(char *arg)
  -static void describe(struct commit *cmit, int last_one)
 ++static void describe(char *arg, int last_one)
   {
  +	unsigned char sha1[20];
  +	struct commit *cmit;
-  	struct commit_list *list;
+	struct commit_list *list;
-  	static int initialized = 0;
+	static int initialized = 0;
-  	struct commit_name *n;
+	struct commit_name *n;
-  
+
  +	if (get_sha1(arg, sha1) < 0)
  +		usage(describe_usage);
  +	cmit = lookup_commit_reference(sha1);
  +	if (!cmit)
  +		usage(describe_usage);
  +
-  	if (!initialized) {
+	if (!initialized) {
-  		initialized = 1;
+		initialized = 1;
-  		for_each_ref(get_name);
+		for_each_ref(get_name);
 ------------
 
 1.   It is preceded with a "git diff" header, that looks like
@@ -233,4 +233,3 @@ parents).  When shown by `git diff-files -c`, it compares the
 two unresolved merge parents with the working tree file
 (i.e. file1 is stage 2 aka "our version", file2 is stage 3 aka
 "their version").
-

Documentation/diff-options.txt

@@ -100,8 +100,8 @@
 	that matches other criteria, nothing is selected.
 
 --find-copies-harder::
-	For performance reasons, by default, -C option finds copies only 
+	For performance reasons, by default, -C option finds copies only
-	if the original file of the copy was modified in the same 
+	if the original file of the copy was modified in the same
 	changeset.  This flag makes the command
 	inspect unmodified files as candidates for the source of
 	copy.  This is a very expensive operation for large

Documentation/diffcore.txt

@@ -71,7 +71,7 @@ The first transformation in the chain is diffcore-pathspec, and
 is controlled by giving the pathname parameters to the
 git-diff-* commands on the command line.  The pathspec is used
 to limit the world diff operates in.  It removes the filepairs
-outside the specified set of pathnames.  E.g. If the input set 
+outside the specified set of pathnames.  E.g. If the input set
 of filepairs included:
 
 ------------------------------------------------
@@ -269,4 +269,3 @@ Documentation
 *.c
 t
 ------------------------------------------------
-

Documentation/docbook-xsl.css

@@ -1,286 +1,286 @@
-/*
+/*
-  CSS stylesheet for XHTML produced by DocBook XSL stylesheets.
+  CSS stylesheet for XHTML produced by DocBook XSL stylesheets.
-  Tested with XSL stylesheets 1.61.2, 1.67.2
+  Tested with XSL stylesheets 1.61.2, 1.67.2
-*/
+*/
-
+
-span.strong {
+span.strong {
-  font-weight: bold;
+  font-weight: bold;
-}
+}
-
+
-body blockquote {
+body blockquote {
-  margin-top: .75em;
+  margin-top: .75em;
-  line-height: 1.5;
+  line-height: 1.5;
-  margin-bottom: .75em;
+  margin-bottom: .75em;
-}
+}
-
+
-html body {
+html body {
-  margin: 1em 5% 1em 5%;
+  margin: 1em 5% 1em 5%;
-  line-height: 1.2;
+  line-height: 1.2;
-}
+}
-
+
-body div {
+body div {
-  margin: 0;
+  margin: 0;
-}
+}
-
+
-h1, h2, h3, h4, h5, h6,
+h1, h2, h3, h4, h5, h6,
-div.toc p b,
+div.toc p b,
-div.list-of-figures p b,
+div.list-of-figures p b,
-div.list-of-tables p b,
+div.list-of-tables p b,
-div.abstract p.title
+div.abstract p.title
-{
+{
-  color: #527bbd;
+  color: #527bbd;
-  font-family: tahoma, verdana, sans-serif;
+  font-family: tahoma, verdana, sans-serif;
-}
+}
-
+
-div.toc p:first-child,
+div.toc p:first-child,
-div.list-of-figures p:first-child,
+div.list-of-figures p:first-child,
-div.list-of-tables p:first-child,
+div.list-of-tables p:first-child,
-div.example p.title
+div.example p.title
-{
+{
-  margin-bottom: 0.2em;
+  margin-bottom: 0.2em;
-}
+}
-
+
-body h1 {
+body h1 {
-  margin: .0em 0 0 -4%;
+  margin: .0em 0 0 -4%;
-  line-height: 1.3;
+  line-height: 1.3;
-  border-bottom: 2px solid silver;
+  border-bottom: 2px solid silver;
-}
+}
-
+
-body h2 {
+body h2 {
-  margin: 0.5em 0 0 -4%;
+  margin: 0.5em 0 0 -4%;
-  line-height: 1.3;
+  line-height: 1.3;
-  border-bottom: 2px solid silver;
+  border-bottom: 2px solid silver;
-}
+}
-
+
-body h3 {
+body h3 {
-  margin: .8em 0 0 -3%;
+  margin: .8em 0 0 -3%;
-  line-height: 1.3;
+  line-height: 1.3;
-}
+}
-
+
-body h4 {
+body h4 {
-  margin: .8em 0 0 -3%;
+  margin: .8em 0 0 -3%;
-  line-height: 1.3;
+  line-height: 1.3;
-}
+}
-
+
-body h5 {
+body h5 {
-  margin: .8em 0 0 -2%;
+  margin: .8em 0 0 -2%;
-  line-height: 1.3;
+  line-height: 1.3;
-}
+}
-
+
-body h6 {
+body h6 {
-  margin: .8em 0 0 -1%;
+  margin: .8em 0 0 -1%;
-  line-height: 1.3;
+  line-height: 1.3;
-}
+}
-
+
-body hr {
+body hr {
-  border: none; /* Broken on IE6 */
+  border: none; /* Broken on IE6 */
-}
+}
-div.footnotes hr {
+div.footnotes hr {
-  border: 1px solid silver;
+  border: 1px solid silver;
-}
+}
-
+
-div.navheader th, div.navheader td, div.navfooter td {
+div.navheader th, div.navheader td, div.navfooter td {
-  font-family: sans-serif;
+  font-family: sans-serif;
-  font-size: 0.9em;
+  font-size: 0.9em;
-  font-weight: bold;
+  font-weight: bold;
-  color: #527bbd;
+  color: #527bbd;
-}
+}
-div.navheader img, div.navfooter img {
+div.navheader img, div.navfooter img {
-  border-style: none;
+  border-style: none;
-}
+}
-div.navheader a, div.navfooter a {
+div.navheader a, div.navfooter a {
-  font-weight: normal;
+  font-weight: normal;
-}
+}
-div.navfooter hr {
+div.navfooter hr {
-  border: 1px solid silver;
+  border: 1px solid silver;
-}
+}
-
+
-body td {
+body td {
-  line-height: 1.2
+  line-height: 1.2
-}
+}
-
+
-body th {
+body th {
-  line-height: 1.2;
+  line-height: 1.2;
-}
+}
-
+
-ol {
+ol {
-  line-height: 1.2;
+  line-height: 1.2;
-}
+}
-
+
-ul, body dir, body menu {
+ul, body dir, body menu {
-  line-height: 1.2;
+  line-height: 1.2;
-}
+}
-
+
-html {
+html {
-  margin: 0; 
+  margin: 0;
-  padding: 0;
+  padding: 0;
-}
+}
-
+
-body h1, body h2, body h3, body h4, body h5, body h6 {
+body h1, body h2, body h3, body h4, body h5, body h6 {
-  margin-left: 0
+  margin-left: 0
-} 
+}
-
+
-body pre {
+body pre {
-  margin: 0.5em 10% 0.5em 1em;
+  margin: 0.5em 10% 0.5em 1em;
-  line-height: 1.0;
+  line-height: 1.0;
-  color: navy;
+  color: navy;
-}
+}
-
+
-tt.literal, code.literal {
+tt.literal, code.literal {
-  color: navy;
+  color: navy;
-}
+}
-
+
-div.literallayout p {
+div.literallayout p {
-  padding: 0em;
+  padding: 0em;
-  margin: 0em;
+  margin: 0em;
-}
+}
-
+
-div.literallayout {
+div.literallayout {
-  font-family: monospace;
+  font-family: monospace;
-#  margin: 0.5em 10% 0.5em 1em;
+#  margin: 0.5em 10% 0.5em 1em;
-  margin: 0em;
+  margin: 0em;
-  color: navy;
+  color: navy;
-  border: 1px solid silver;
+  border: 1px solid silver;
-  background: #f4f4f4;
+  background: #f4f4f4;
-  padding: 0.5em;
+  padding: 0.5em;
-}
+}
-
+
-.programlisting, .screen {
+.programlisting, .screen {
-  border: 1px solid silver;
+  border: 1px solid silver;
-  background: #f4f4f4;
+  background: #f4f4f4;
-  margin: 0.5em 10% 0.5em 0;
+  margin: 0.5em 10% 0.5em 0;
-  padding: 0.5em 1em;
+  padding: 0.5em 1em;
-}
+}
-
+
-div.sidebar {
+div.sidebar {
-  background: #ffffee;
+  background: #ffffee;
-  margin: 1.0em 10% 0.5em 0;
+  margin: 1.0em 10% 0.5em 0;
-  padding: 0.5em 1em;
+  padding: 0.5em 1em;
-  border: 1px solid silver;
+  border: 1px solid silver;
-}
+}
-div.sidebar * { padding: 0; }
+div.sidebar * { padding: 0; }
-div.sidebar div { margin: 0; }
+div.sidebar div { margin: 0; }
-div.sidebar p.title {
+div.sidebar p.title {
-  font-family: sans-serif;
+  font-family: sans-serif;
-  margin-top: 0.5em;
+  margin-top: 0.5em;
-  margin-bottom: 0.2em;
+  margin-bottom: 0.2em;
-}
+}
-
+
-div.bibliomixed {
+div.bibliomixed {
-  margin: 0.5em 5% 0.5em 1em;
+  margin: 0.5em 5% 0.5em 1em;
-}
+}
-
+
-div.glossary dt {
+div.glossary dt {
-  font-weight: bold;
+  font-weight: bold;
-}
+}
-div.glossary dd p {
+div.glossary dd p {
-  margin-top: 0.2em;
+  margin-top: 0.2em;
-}
+}
-
+
-dl {
+dl {
-  margin: .8em 0;
+  margin: .8em 0;
-  line-height: 1.2;
+  line-height: 1.2;
-}
+}
-
+
-dt {
+dt {
-  margin-top: 0.5em;
+  margin-top: 0.5em;
-}
+}
-
+
-dt span.term {
+dt span.term {
-  font-style: italic;
+  font-style: italic;
-}
+}
-
+
-div.variablelist dd p {
+div.variablelist dd p {
-  margin-top: 0;
+  margin-top: 0;
-}
+}
-
+
-div.itemizedlist li, div.orderedlist li {
+div.itemizedlist li, div.orderedlist li {
-  margin-left: -0.8em;
+  margin-left: -0.8em;
-  margin-top: 0.5em;
+  margin-top: 0.5em;
-}
+}
-
+
-ul, ol {
+ul, ol {
-    list-style-position: outside;
+    list-style-position: outside;
-}
+}
-
+
-div.sidebar ul, div.sidebar ol {
+div.sidebar ul, div.sidebar ol {
-    margin-left: 2.8em;
+    margin-left: 2.8em;
-}
+}
-
+
-div.itemizedlist p.title,
+div.itemizedlist p.title,
-div.orderedlist p.title,
+div.orderedlist p.title,
-div.variablelist p.title
+div.variablelist p.title
-{
+{
-  margin-bottom: -0.8em;
+  margin-bottom: -0.8em;
-}
+}
-
+
-div.revhistory table {
+div.revhistory table {
-  border-collapse: collapse;
+  border-collapse: collapse;
-  border: none;
+  border: none;
-}
+}
-div.revhistory th {
+div.revhistory th {
-  border: none;
+  border: none;
-  color: #527bbd;
+  color: #527bbd;
-  font-family: tahoma, verdana, sans-serif;
+  font-family: tahoma, verdana, sans-serif;
-}
+}
-div.revhistory td {
+div.revhistory td {
-  border: 1px solid silver;
+  border: 1px solid silver;
-}
+}
-
+
-/* Keep TOC and index lines close together. */
+/* Keep TOC and index lines close together. */
-div.toc dl, div.toc dt,
+div.toc dl, div.toc dt,
-div.list-of-figures dl, div.list-of-figures dt,
+div.list-of-figures dl, div.list-of-figures dt,
-div.list-of-tables dl, div.list-of-tables dt,
+div.list-of-tables dl, div.list-of-tables dt,
-div.indexdiv dl, div.indexdiv dt
+div.indexdiv dl, div.indexdiv dt
-{
+{
-  line-height: normal;
+  line-height: normal;
-  margin-top: 0;
+  margin-top: 0;
-  margin-bottom: 0;
+  margin-bottom: 0;
-}
+}
-
+
-/*
+/*
-  Table styling does not work because of overriding attributes in
+  Table styling does not work because of overriding attributes in
-  generated HTML.
+  generated HTML.
-*/
+*/
-div.table table,
+div.table table,
-div.informaltable table
+div.informaltable table
-{
+{
-    margin-left: 0;
+    margin-left: 0;
-    margin-right: 5%;
+    margin-right: 5%;
-    margin-bottom: 0.8em;
+    margin-bottom: 0.8em;
-}
+}
-div.informaltable table
+div.informaltable table
-{
+{
-    margin-top: 0.4em
+    margin-top: 0.4em
-}
+}
-div.table thead,
+div.table thead,
-div.table tfoot,
+div.table tfoot,
-div.table tbody,
+div.table tbody,
-div.informaltable thead,
+div.informaltable thead,
-div.informaltable tfoot,
+div.informaltable tfoot,
-div.informaltable tbody
+div.informaltable tbody
-{
+{
-    /* No effect in IE6. */
+    /* No effect in IE6. */
-    border-top: 2px solid #527bbd;
+    border-top: 2px solid #527bbd;
-    border-bottom: 2px solid #527bbd;
+    border-bottom: 2px solid #527bbd;
-}
+}
-div.table thead, div.table tfoot,
+div.table thead, div.table tfoot,
-div.informaltable thead, div.informaltable tfoot
+div.informaltable thead, div.informaltable tfoot
-{
+{
-    font-weight: bold;
+    font-weight: bold;
-}
+}
-
+
-div.mediaobject img {
+div.mediaobject img {
-    border: 1px solid silver;
+    border: 1px solid silver;
-    margin-bottom: 0.8em;
+    margin-bottom: 0.8em;
-}
+}
-div.figure p.title,
+div.figure p.title,
-div.table p.title
+div.table p.title
-{
+{
-  margin-top: 1em;
+  margin-top: 1em;
-  margin-bottom: 0.4em;
+  margin-bottom: 0.4em;
-}
+}
-
+
-@media print {
+@media print {
-  div.navheader, div.navfooter { display: none; }
+  div.navheader, div.navfooter { display: none; }
-}
+}

Documentation/fetch-options.txt

@@ -52,4 +52,3 @@
 	Deepen the history of a 'shallow' repository created by
 	`git clone` with `--depth=<depth>` option (see gitlink:git-clone[1])
 	by the specified number of commits.
-

Documentation/git-add.txt

@@ -228,4 +228,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-am.txt

@@ -158,4 +158,3 @@ Documentation by Petr Baudis, Junio C Hamano and the git-list <git@vger.kernel.o
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-apply.txt

@@ -183,4 +183,3 @@ Documentation by Junio C Hamano
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-archimport.txt

@@ -17,26 +17,26 @@ DESCRIPTION
 Imports a project from one or more Arch repositories. It will follow branches
 and repositories within the namespaces defined by the <archive/branch>
 parameters supplied. If it cannot find the remote branch a merge comes from
-it will just import it as a regular commit. If it can find it, it will mark it 
+it will just import it as a regular commit. If it can find it, it will mark it
-as a merge whenever possible (see discussion below). 
+as a merge whenever possible (see discussion below).
 
-The script expects you to provide the key roots where it can start the import 
+The script expects you to provide the key roots where it can start the import
-from an 'initial import' or 'tag' type of Arch commit. It will follow and 
+from an 'initial import' or 'tag' type of Arch commit. It will follow and
-import new branches within the provided roots. 
+import new branches within the provided roots.
 
-It expects to be dealing with one project only. If it sees 
+It expects to be dealing with one project only. If it sees
-branches that have different roots, it will refuse to run. In that case, 
+branches that have different roots, it will refuse to run. In that case,
-edit your <archive/branch> parameters to define clearly the scope of the 
+edit your <archive/branch> parameters to define clearly the scope of the
-import. 
+import.
 
-`git-archimport` uses `tla` extensively in the background to access the 
+`git-archimport` uses `tla` extensively in the background to access the
 Arch repository.
 Make sure you have a recent version of `tla` available in the path. `tla` must
-know about the repositories you pass to `git-archimport`. 
+know about the repositories you pass to `git-archimport`.
 
-For the initial import `git-archimport` expects to find itself in an empty 
+For the initial import `git-archimport` expects to find itself in an empty
-directory. To follow the development of a project that uses Arch, rerun 
+directory. To follow the development of a project that uses Arch, rerun
-`git-archimport` with the same parameters as the initial import to perform 
+`git-archimport` with the same parameters as the initial import to perform
 incremental imports.
 
 While git-archimport will try to create sensible branch names for the
@@ -54,15 +54,15 @@ convert Arch repositories that had been rotated periodically.
 
 MERGES
 ------
-Patch merge data from Arch is used to mark merges in git as well. git 
+Patch merge data from Arch is used to mark merges in git as well. git
 does not care much about tracking patches, and only considers a merge when a
 branch incorporates all the commits since the point they forked. The end result
-is that git will have a good idea of how far branches have diverged. So the 
+is that git will have a good idea of how far branches have diverged. So the
 import process does lose some patch-trading metadata.
 
-Fortunately, when you try and merge branches imported from Arch, 
+Fortunately, when you try and merge branches imported from Arch,
-git will find a good merge base, and it has a good chance of identifying 
+git will find a good merge base, and it has a good chance of identifying
-patches that have been traded out-of-sequence between the branches. 
+patches that have been traded out-of-sequence between the branches.
 
 OPTIONS
 -------
@@ -71,10 +71,10 @@ OPTIONS
 	Display usage.
 
 -v::
-	Verbose output. 
+	Verbose output.
 
 -T::
-	Many tags. Will create a tag for every commit, reflecting the commit 
+	Many tags. Will create a tag for every commit, reflecting the commit
 	name in the Arch repository.
 
 -f::
@@ -104,7 +104,7 @@ OPTIONS
 
 
 <archive/branch>::
-	Archive/branch identifier in a format that `tla log` understands. 
+	Archive/branch identifier in a format that `tla log` understands.
 
 
 Author
@@ -118,4 +118,3 @@ Documentation by Junio C Hamano, Martin Langhoff and the git-list <git@vger.kern
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-bisect.txt

@@ -8,7 +8,7 @@ git-bisect - Find the change that introduced a bug by binary search
 
 SYNOPSIS
 --------
-'git bisect' <subcommand> <options> 
+'git bisect' <subcommand> <options>
 
 DESCRIPTION
 -----------
@@ -200,4 +200,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-branch.txt

@@ -158,4 +158,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-cat-file.txt

@@ -71,4 +71,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-check-attr.txt

@@ -34,4 +34,3 @@ Documentation by James Bowes.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-checkout-index.txt

@@ -182,4 +182,3 @@ Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-checkout.txt

@@ -215,4 +215,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-cherry-pick.txt

@@ -68,4 +68,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-cherry.txt

@@ -64,4 +64,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-clone.txt

@@ -175,4 +175,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-commit-tree.txt

@@ -40,7 +40,7 @@ OPTIONS
 
 -p <parent commit>::
 	Each '-p' indicates the id of a parent commit object.
-	
+
 
 Commit Information
 ------------------
@@ -107,4 +107,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-config.txt

@@ -291,4 +291,3 @@ Documentation by Johannes Schindelin, Petr Baudis and the git-list <git@vger.ker
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-convert-objects.txt

@@ -26,4 +26,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-count-objects.txt

@@ -35,4 +35,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-cvsexportcommit.txt

@@ -14,19 +14,19 @@ SYNOPSIS
 DESCRIPTION
 -----------
 Exports a commit from GIT to a CVS checkout, making it easier
-to merge patches from a git repository into a CVS repository. 
+to merge patches from a git repository into a CVS repository.
 
-Execute it from the root of the CVS working copy. GIT_DIR must be defined. 
+Execute it from the root of the CVS working copy. GIT_DIR must be defined.
 See examples below.
 
-It does its best to do the safe thing, it will check that the files are 
+It does its best to do the safe thing, it will check that the files are
-unchanged and up to date in the CVS checkout, and it will not autocommit 
+unchanged and up to date in the CVS checkout, and it will not autocommit
 by default.
 
 Supports file additions, removals, and commits that affect binary files.
 
 If the commit is a merge commit, you must tell git-cvsexportcommit what parent
-should the changeset be done against. 
+should the changeset be done against.
 
 OPTIONS
 -------
@@ -55,7 +55,7 @@ OPTIONS
 	Force the parent commit, even if it is not a direct parent.
 
 -m::
-	Prepend the commit message with the provided prefix. 
+	Prepend the commit message with the provided prefix.
 	Useful for patch series and the like.
 
 -u::
@@ -73,7 +73,7 @@ Merge one patch into CVS::
 $ export GIT_DIR=~/project/.git
 $ cd ~/project_cvs_checkout
 $ git-cvsexportcommit -v <commit-sha1>
-$ cvs commit -F .mgs <files> 
+$ cvs commit -F .mgs <files>
 ------------
 
 Merge pending patches into CVS automatically -- only if you really know what you are doing ::
@@ -95,4 +95,3 @@ Documentation by Martin Langhoff <martin@catalyst.net.nz>
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-cvsimport.txt

@@ -37,7 +37,7 @@ OPTIONS
 
 -d <CVSROOT>::
 	The root of the CVS archive. May be local (a simple path) or remote;
-	currently, only the :local:, :ext: and :pserver: access methods 
+	currently, only the :local:, :ext: and :pserver: access methods
 	are supported. If not given, git-cvsimport will try to read it
 	from `CVS/Root`. If no such file exists, it checks for the
 	`CVSROOT` environment variable.
@@ -67,7 +67,7 @@ the old cvs2git tool.
 -k::
 	Kill keywords: will extract files with '-kk' from the CVS archive
 	to avoid noisy changesets. Highly recommended, but off by default
-	to preserve compatibility with early imported trees. 
+	to preserve compatibility with early imported trees.
 
 -u::
 	Convert underscores in tag and branch names to dots.
@@ -89,15 +89,15 @@ If you need to pass multiple options, separate them with a comma.
 	Instead of calling cvsps, read the provided cvsps output file. Useful
 	for debugging or when cvsps is being handled outside cvsimport.
 
--m::    
+-m::
 	Attempt to detect merges based on the commit message. This option
-	will enable default regexes that try to capture the name source 
+	will enable default regexes that try to capture the name source
-	branch name from the commit message. 
+	branch name from the commit message.
 
 -M <regex>::
 	Attempt to detect merges based on the commit message with a custom
 	regex. It can be used with '-m' to also see the default regexes.
-	You must escape forward slashes. 
+	You must escape forward slashes.
 
 -S <regex>::
 	Skip paths matching the regex.
@@ -156,4 +156,3 @@ Documentation by Matthias Urlichs <smurf@smurf.noris.de>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-daemon.txt

@@ -235,4 +235,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-describe.txt

@@ -124,4 +124,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-diff-files.txt

@@ -26,7 +26,7 @@ include::diff-options.txt[]
 	branch" respectively.  With these options, diffs for
 	merged entries are not shown.
 +
-The default is to diff against our branch (-2) and the 
+The default is to diff against our branch (-2) and the
 cleanly resolved paths.  The option -0 can be given to
 omit diff output for unmerged entries and just show "Unmerged".
 
@@ -58,4 +58,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-diff-index.txt

@@ -75,7 +75,7 @@ actually doing a "git-write-tree" and comparing that. Except this one is much
 nicer for the case where you just want to check where you are.
 
 So doing a "git-diff-index --cached" is basically very useful when you are
-asking yourself "what have I already marked for being committed, and 
+asking yourself "what have I already marked for being committed, and
 what's the difference to a previous tree".
 
 Non-cached Mode
@@ -130,4 +130,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-diff-tree.txt

@@ -166,4 +166,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-diff.txt

@@ -138,4 +138,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-fast-import.txt

@@ -908,4 +908,3 @@ Documentation by Shawn O. Pearce <spearce@spearce.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-fmt-merge-msg.txt

@@ -60,4 +60,3 @@ Documentation by Petr Baudis, Junio C Hamano and the git-list <git@vger.kernel.o
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-format-patch.txt

@@ -178,4 +178,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-fsck.txt

@@ -145,4 +145,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-get-tar-commit-id.txt

@@ -34,4 +34,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-grep.txt

@@ -144,4 +144,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-hash-object.txt

@@ -18,7 +18,7 @@ work tree), and optionally writes the resulting object into the
 object database.  Reports its object ID to its standard output.
 This is used by "git-cvsimport" to update the index
 without modifying files in the work tree.  When <type> is not
-specified, it defaults to "blob". 
+specified, it defaults to "blob".
 
 OPTIONS
 -------
@@ -43,4 +43,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-http-fetch.txt

@@ -54,4 +54,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-http-push.txt

@@ -52,7 +52,7 @@ Specifying the Refs
 
 A '<ref>' specification can be either a single pattern, or a pair
 of such patterns separated by a colon ":" (this means that a ref name
-cannot have a colon in it).  A single pattern '<name>' is just a 
+cannot have a colon in it).  A single pattern '<name>' is just a
 shorthand for '<name>:<name>'.
 
 Each pattern pair consists of the source side (before the colon)

Documentation/git-index-pack.txt

@@ -98,4 +98,3 @@ Documentation by Sergey Vlasov
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-init-db.txt

@@ -16,4 +16,3 @@ DESCRIPTION
 
 This is a synonym for gitlink:git-init[1].  Please refer to the
 documentation of that command.
-

Documentation/git-init.txt

@@ -108,4 +108,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-instaweb.txt

@@ -82,4 +82,3 @@ Documentation by Eric Wong <normalperson@yhbt.net>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-local-fetch.txt

@@ -62,4 +62,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-log.txt

@@ -101,4 +101,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-ls-files.txt

@@ -180,4 +180,3 @@ Documentation by David Greaves, Junio C Hamano, Josh Triplett, and the git-list
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-ls-remote.txt

@@ -70,4 +70,3 @@ Written by Junio C Hamano <junkio@cox.net>
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-ls-tree.txt

@@ -92,4 +92,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-mailinfo.txt

@@ -67,4 +67,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-mailsplit.txt

@@ -56,4 +56,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-merge-base.txt

@@ -40,4 +40,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-merge-index.txt

@@ -59,7 +59,7 @@ Examples:
   This is modified MM in the branch B.			# merge2
   This is modified MM in the branch B.			# current contents
 
-or 
+or
 
   torvalds@ppc970:~/merge-test> git-merge-index cat AA MM
   cat: : No such file or directory
@@ -85,4 +85,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-merge-one-file.txt

@@ -27,4 +27,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-merge-tree.txt

@@ -34,4 +34,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-merge.txt

@@ -95,7 +95,7 @@ When things cleanly merge, these things happen:
 1. the results are updated both in the index file and in your
    working tree,
 2. index file is written out as a tree,
-3. the tree gets committed, and 
+3. the tree gets committed, and
 4. the `HEAD` pointer gets advanced.
 
 Because of 2., we require that the original state of the index

Documentation/git-mergetool.txt

@@ -43,4 +43,3 @@ Documentation by Theodore Y Ts'o.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-mktag.txt

@@ -44,4 +44,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-mktree.txt

@@ -32,4 +32,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-mv.txt

@@ -51,4 +51,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-name-rev.txt

@@ -76,4 +76,3 @@ Documentation by Johannes Schindelin.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-p4import.txt

@@ -165,4 +165,3 @@ Written by Sean Estabrooks <seanlkml@sympatico.ca>
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-pack-objects.txt

@@ -185,4 +185,3 @@ gitlink:git-prune-packed[1]
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-pack-redundant.txt

@@ -17,7 +17,7 @@ are redundant. The output is suitable for piping to
 'xargs rm' if you are in the root of the repository.
 
 git-pack-redundant accepts a list of objects on standard input. Any objects
-given will be ignored when checking which packs are required. This makes the 
+given will be ignored when checking which packs are required. This makes the
 following command useful when wanting to remove packs which contain unreachable
 objects.
 
@@ -55,4 +55,3 @@ gitlink:git-prune-packed[1]
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-patch-id.txt

@@ -40,4 +40,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-peek-remote.txt

@@ -52,4 +52,3 @@ Documentation by Junio C Hamano.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-prune-packed.txt

@@ -50,4 +50,3 @@ gitlink:git-repack[1]
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-prune.txt

@@ -58,4 +58,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-pull.txt

@@ -165,4 +165,3 @@ Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-push.txt

@@ -110,4 +110,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-quiltimport.txt

@@ -58,4 +58,3 @@ Documentation by Eric Biederman <ebiederm@lnxi.com>
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-read-tree.txt

@@ -356,4 +356,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-rebase.txt

@@ -237,4 +237,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-reflog.txt

@@ -65,4 +65,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-relink.txt

@@ -34,4 +34,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-remote.txt

@@ -128,4 +128,3 @@ Documentation by J. Bruce Fields and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-repack.txt

@@ -101,4 +101,3 @@ gitlink:git-prune-packed[1]
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-request-pull.txt

@@ -37,4 +37,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-rev-parse.txt

@@ -286,4 +286,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-revert.txt

@@ -56,4 +56,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-rm.txt

@@ -95,4 +95,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-runstatus.txt

@@ -66,4 +66,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-send-email.txt

@@ -78,7 +78,7 @@ The --cc option must be repeated for each user you want on the cc list.
 	`localhost` otherwise.
 
 --subject::
-   	Specify the initial subject of the email thread.
+	Specify the initial subject of the email thread.
 	Only necessary if --compose is also set.  If --compose
 	is not set, this will be prompted for.
 
@@ -137,4 +137,3 @@ Documentation by Ryan Anderson
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-sh-setup.txt

@@ -69,4 +69,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-shell.txt

@@ -32,4 +32,3 @@ Documentation by Petr Baudis and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-shortlog.txt

@@ -56,4 +56,3 @@ Documentation by Junio C Hamano.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-show-index.txt

@@ -32,4 +32,3 @@ Documentation by Junio C Hamano
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-show.txt

@@ -84,4 +84,3 @@ This manual page is a stub. You can help the git documentation by expanding it.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-ssh-fetch.txt

@@ -48,4 +48,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-ssh-upload.txt

@@ -44,4 +44,3 @@ Documentation by Daniel Barkalow
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-status.txt

@@ -58,4 +58,3 @@ Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-stripspace.txt

@@ -30,4 +30,3 @@ Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-

Documentation/git-svnimport.txt

@@ -174,4 +174,3 @@ Documentation by Matthias Urlichs <smurf@smurf.noris.de>.
 GIT
 ---
 Part of the gitlink:git[7] suite
-