git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.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 16:31:30 -0800	[thread overview]
Message-ID: <20131120003130.GC4212@google.com> (raw)
In-Reply-To: <1384906483-15260-1-git-send-email-jstjohn@purdue.edu>

Hi,

Jason St. John wrote:

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

I'd leave out the above two description lines, since they're redundant
next to the patch text.

> 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.

Interesting.  Alas, I can't reproduce this.

Are you sure it is AsciiDoc that misinterprets the document, and not,
e.g., the predecessor of asciidoctor in gitscm-next?

Do

  Documentation/git-check-attr.txt
  Documentation/git-commit.txt
  Documentation/git-cvsserver.txt
  Documentation/git-p4.txt
  Documentation/git-svn.txt
  Documentation/gitcli.txt
  Documentation/gitweb.txt
  Documentation/mailmap.txt
  
avoid this problem?

Thanks and hope that helps,
Jonathan

  reply	other threads:[~2013-11-20  0:31 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 [this message]
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=20131120003130.GC4212@google.com \
    --to=jrnieder@gmail.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 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).