From: Andreas Schwab <schwab@linux-m68k.org>
To: Jeff King <peff@peff.net>
Cc: Lars Schneider <larsxschneider@gmail.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Minor man page weirdness?
Date: Tue, 17 Oct 2017 19:25:28 +0200 [thread overview]
Message-ID: <878tg9u1o7.fsf@linux-m68k.org> (raw)
In-Reply-To: <20171017163828.igmlsbdynpe6m37w@sigill.intra.peff.net> (Jeff King's message of "Tue, 17 Oct 2017 12:38:29 -0400")
On Okt 17 2017, Jeff King <peff@peff.net> wrote:
> On Tue, Oct 17, 2017 at 06:29:59PM +0200, Andreas Schwab wrote:
>
>> On Okt 16 2017, Jeff King <peff@peff.net> wrote:
>>
>> > I get:
>> >
>> > Reset <branchname> to <startpoint> if <branchname> exists already\&. Without
>> > \fB\-f\fR
>> > \fIgit branch\fR
>> > refuses to change an existing branch\&. In combination with
>>
>> I see this in git-branch.1:
>>
>> Reset <branchname> to <startpoint> if <branchname> exists already\&. Without
>> \fB\-f\fR\fIgit branch\fR
>> refuses to change an existing branch\&. In combination with
>>
>> This is with asciidoc 8.6.9.
>
> Thanks, that seems a likely culprit, then. What's in your git-branch.xml
> after you build the documentation?
Same as yours, with the space. I'd guess it's rather xmlto (version
0.0.25) that's the culprit here.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-10-17 17:25 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878tg9u1o7.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=peff@peff.net \
/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).