git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jason St. John" <jstjohn@purdue.edu>
To: git@vger.kernel.org
Cc: "Jason St. John" <jstjohn@purdue.edu>
Subject: [PATCH] Fix typesetting in Bugs section of 'git-rebase' man page (web version)
Date: Tue, 19 Nov 2013 19:14:43 -0500	[thread overview]
Message-ID: <1384906483-15260-1-git-send-email-jstjohn@purdue.edu> (raw)

Documentation/git-rebase.txt: add a blank line after the two AsciiDoc
    listing blocks

Without these blank lines, AsciiDoc thinks the opening "-----" is a
section heading and typesets the word "to" as such, which causes
cascading formatting/typesetting issues until the end of the document.

Signed-off-by: Jason St. John <jstjohn@purdue.edu>
---
You can see the carnage here:
http://git-scm.com/docs/git-rebase#_bugs

This fixes GitHub issue github/gitscm-next#281
https://github.com/github/gitscm-next/issues/281


 Documentation/git-rebase.txt | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
index 94e07fd..88d0afb 100644
--- a/Documentation/git-rebase.txt
+++ b/Documentation/git-rebase.txt
@@ -743,9 +743,11 @@ For example, an attempt to rearrange
 1 --- 2 --- 3 --- 4 --- 5
 ------------
 to
+
 ------------
 1 --- 2 --- 4 --- 3 --- 5
 ------------
+
 by moving the "pick 4" line will result in the following history:
 ------------
 	3
-- 
1.8.4.2

             reply	other threads:[~2013-11-20  0:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20  0:14 Jason St. John [this message]
2013-11-20  0:31 ` [PATCH] Fix typesetting in Bugs section of 'git-rebase' man page (web version) Jonathan Nieder
2013-11-20  1:12   ` Jason St. John
2013-11-20  1:24     ` Jonathan Nieder
2013-11-20  4:43 ` Junio C Hamano
2014-01-11  1:25   ` Jason St. John
2014-01-13 17:55     ` Junio C Hamano
2014-01-15  5:36       ` Jason St. John
2014-01-15 11:29         ` Kyle J. McKay
2014-01-16  0:29           ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1384906483-15260-1-git-send-email-jstjohn@purdue.edu \
    --to=jstjohn@purdue.edu \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).