From: Junio C Hamano <gitster@pobox.com>
To: "Jason St. John" <jstjohn@purdue.edu>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix typesetting in Bugs section of 'git-rebase' man page (web version)
Date: Tue, 19 Nov 2013 20:43:53 -0800 [thread overview]
Message-ID: <xmqqwqk37kdy.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1384906483-15260-1-git-send-email-jstjohn@purdue.edu> (Jason St. John's message of "Tue, 19 Nov 2013 19:14:43 -0500")
"Jason St. John" <jstjohn@purdue.edu> writes:
> Documentation/git-rebase.txt: add a blank line after the two AsciiDoc
> listing blocks
That looks funnily formatted, out of place and redundant.
> 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
Hmph. https://git-htmldocs.googlecode.com/git/git.html has HTML
documentation pages I preformat, but as far as I can see, the bugs
section of git-rebase(1) does not have such a "carnage".
Perhaps git-scm.com uses some buggy formatter?
next prev parent reply other threads:[~2013-11-20 4:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 0:14 [PATCH] Fix typesetting in Bugs section of 'git-rebase' man page (web version) Jason St. John
2013-11-20 0:31 ` 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 [this message]
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=xmqqwqk37kdy.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jstjohn@purdue.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.