Merge branch 'xf/user-manual-markup' into maint

AsciiDoc markup fixes. * xf/user-manual-markup: Documentation: match undefline with the text in old release notes Documentation: match underline with the text Documentation: fix header markup
9 years ago · 6c66686e0b
11 changed files with 11 additions and 11 deletions
--- a/Documentation/RelNotes/1.8.3.1.txt
+++ b/Documentation/RelNotes/1.8.3.1.txt
@ -1,5 +1,5 @@
				@@ -1,5 +1,5 @@
 Git v1.8.3.1 Release Notes
-========================
+==========================

 Fixes since v1.8.3
 ------------------
--- a/Documentation/RelNotes/1.8.4.1.txt
+++ b/Documentation/RelNotes/1.8.4.1.txt
@ -1,5 +1,5 @@
				@@ -1,5 +1,5 @@
 Git v1.8.4.1 Release Notes
-========================
+==========================

 Fixes since v1.8.4
 ------------------
--- a/Documentation/RelNotes/1.8.4.2.txt
+++ b/Documentation/RelNotes/1.8.4.2.txt
@ -1,5 +1,5 @@
				@@ -1,5 +1,5 @@
 Git v1.8.4.2 Release Notes
-========================
+==========================

 Fixes since v1.8.4.1
 --------------------
--- a/Documentation/RelNotes/1.8.4.3.txt
+++ b/Documentation/RelNotes/1.8.4.3.txt
@ -1,5 +1,5 @@
				@@ -1,5 +1,5 @@
 Git v1.8.4.3 Release Notes
-========================
+==========================

 Fixes since v1.8.4.2
 --------------------
--- a/Documentation/RelNotes/1.8.4.4.txt
+++ b/Documentation/RelNotes/1.8.4.4.txt
@ -1,5 +1,5 @@
				@@ -1,5 +1,5 @@
 Git v1.8.4.4 Release Notes
-========================
+==========================

 Fixes since v1.8.4.3
 --------------------
--- a/Documentation/git-bisect.txt
+++ b/Documentation/git-bisect.txt
@ -174,7 +174,7 @@ Then compile and test the chosen revision, and afterwards mark
				@@ -174,7 +174,7 @@ Then compile and test the chosen revision, and afterwards mark
 the revision as good or bad in the usual manner.

 Bisect skip
-~~~~~~~~~~~~
+~~~~~~~~~~~

 Instead of choosing a nearby commit by yourself, you can ask Git to do
 it for you by issuing the command:
--- a/Documentation/git-remote.txt
+++ b/Documentation/git-remote.txt
@ -1,5 +1,5 @@
				@@ -1,5 +1,5 @@
 git-remote(1)
-============
+=============

 NAME
 ----
--- a/Documentation/git-upload-archive.txt
+++ b/Documentation/git-upload-archive.txt
@ -1,5 +1,5 @@
				@@ -1,5 +1,5 @@
 git-upload-archive(1)
-====================
+=====================

 NAME
 ----
--- a/Documentation/gitrevisions.txt
+++ b/Documentation/gitrevisions.txt
@ -1,5 +1,5 @@
				@@ -1,5 +1,5 @@
 gitrevisions(7)
-================
+===============

 NAME
 ----
--- a/Documentation/urls-remotes.txt
+++ b/Documentation/urls-remotes.txt
@ -36,7 +36,7 @@ The `<pushurl>` is used for pushes only. It is optional and defaults
				@@ -36,7 +36,7 @@ The `<pushurl>` is used for pushes only. It is optional and defaults
 to `<url>`.

 Named file in `$GIT_DIR/remotes`
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 You can choose to provide the name of a
 file in `$GIT_DIR/remotes`.  The URL
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@ -1491,7 +1491,7 @@ resolving a merge>>.
				@@ -1491,7 +1491,7 @@ resolving a merge>>.

 [[fixing-a-mistake-by-rewriting-history]]
 Fixing a mistake by rewriting history
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 If the problematic commit is the most recent commit, and you have not
 yet made that commit public, then you may just