git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
	Lars Schneider <larsxschneider@gmail.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Minor man page weirdness?
Date: Wed, 18 Oct 2017 00:01:46 -0400	[thread overview]
Message-ID: <20171018040146.xuhchqtmzqzkzbgf@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqbml5ktrk.fsf@gitster.mtv.corp.google.com>

On Wed, Oct 18, 2017 at 12:41:03PM +0900, Junio C Hamano wrote:

> Jeff King <peff@peff.net> writes:
> 
> > It does make me wonder if there are other instances of the missing-space
> > problem lurking. Grepping for backtick followed by single-quote shows
> > only one more case in user-manual.txt. I have no idea if that one hits
> > the same problem on older docbook versions.
> 
> I had an impression that this is only for roff, but we do not
> produce user-manual.[0-9], do we?

Yeah, I think you're right. We do produce XML of it, but it goes to
other formats like texi and pdf (and if this is a docbook bug, it may or
may not be present in those other output formats).

-Peff

  reply	other threads:[~2017-10-18  4:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 14:16 Minor man page weirdness? Lars Schneider
2017-10-16 22:56 ` Jeff King
2017-10-17 16:29   ` Andreas Schwab
2017-10-17 16:38     ` Jeff King
2017-10-17 17:25       ` Andreas Schwab
2017-10-17 17:29         ` Jeff King
2017-10-17 17:52           ` Andreas Schwab
2017-10-17 19:11             ` Jeff King
2017-10-17 20:03               ` Andreas Schwab
2017-10-17 18:00   ` Andreas Schwab
2017-10-17 20:58     ` Junio C Hamano
2017-10-18  2:34       ` Junio C Hamano
2017-10-18  3:21         ` Jeff King
2017-10-18  3:41           ` Junio C Hamano
2017-10-18  4:01             ` Jeff King [this message]
2017-10-19 22:29           ` Lars Schneider

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=20171018040146.xuhchqtmzqzkzbgf@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=larsxschneider@gmail.com \
    --cc=schwab@linux-m68k.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).