From: Gerrit Pape <pape@smarden.org>
To: git@vger.kernel.org
Subject: Re: spurious .sp in manpages
Date: Wed, 13 Dec 2006 10:17:28 +0000 [thread overview]
Message-ID: <20061213101728.18138.qmail@017513e6f43450.315fe32.mid.smarden.org> (raw)
In-Reply-To: <7vodq8kw97.fsf@assigned-by-dhcp.cox.net>
On Wed, Dec 13, 2006 at 12:58:28AM -0800, Junio C Hamano wrote:
> This is just a random hack to work around problems people seem
> to be seeing in manpage backend of xmlto (it appears we are
> getting ".sp" at the end of line without line break).
>
> Could people test this out?
The workaround works fine for me on Debian/unstable.
next prev parent reply other threads:[~2006-12-13 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 8:58 spurious .sp in manpages Junio C Hamano
2006-12-13 10:17 ` Gerrit Pape [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-16 9:52 Tom Prince
2006-12-16 12:08 ` 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
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=20061213101728.18138.qmail@017513e6f43450.315fe32.mid.smarden.org \
--to=pape@smarden.org \
--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.
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).