From: Lars Schneider <larsxschneider@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Andreas Schwab <schwab@linux-m68k.org>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Minor man page weirdness?
Date: Fri, 20 Oct 2017 00:29:21 +0200 [thread overview]
Message-ID: <A34B4C99-94FD-4EF2-AE60-0522D621BAE6@gmail.com> (raw)
In-Reply-To: <20171018032103.p6bz7wciiedokiyy@sigill.intra.peff.net>
> On 18 Oct 2017, at 05:21, Jeff King <peff@peff.net> wrote:
>
> On Wed, Oct 18, 2017 at 11:34:31AM +0900, Junio C Hamano wrote:
>
>> -- >8 --
>> branch doc: sprinkle a few commas for readability
>>
>> The "--force" option can also be used when the named branch does not
>> yet exist, and the point of the option is the user can (re)point the
>> branch to the named commit even if it does. Add 'even' before 'if'
>> to clarify. Also, insert another comma after "Without -f" before
>> "the command refuses..." to make the text easier to parse.
>>
>> Incidentally, this change should help certain versions of
>> docbook-xsl-stylesheets that renders the original without any
>> whitespace between "-f" and "git".
>
> Thanks, this looks good.
To me, too! Thanks for investigating and fixing the issue :-)
- Lars
prev parent reply other threads:[~2017-10-19 22:29 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
2017-10-19 22:29 ` Lars Schneider [this message]
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=A34B4C99-94FD-4EF2-AE60-0522D621BAE6@gmail.com \
--to=larsxschneider@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--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).