From: Junio C Hamano <gitster@pobox.com>
To: "Jean-Noël Avila" <jn.avila@free.fr>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] doc: tidy asciidoc style
Date: Wed, 23 Jan 2019 11:43:35 -0800 [thread overview]
Message-ID: <xmqqfttjb1nc.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <xmqqk1ivb1yp.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Wed, 23 Jan 2019 11:36:46 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Jean-Noël Avila <jn.avila@free.fr> writes:
>
>> This mainly refers to enforcing indentation on additional lines of
>> items of lists.
>>
>> Signed-off-by: Jean-Noël Avila <jn.avila@free.fr>
>> ---
>
> I somehow misread the title as "tiny asciidoc style (fixes)". This
> is a huge clean-up. Thanks for working on it.
>
>> diff --git a/Documentation/git-add.txt b/Documentation/git-add.txt
>> index 45652fe4a6..37bcab94d5 100644
>> --- a/Documentation/git-add.txt
>> +++ b/Documentation/git-add.txt
>> @@ -58,9 +58,9 @@ OPTIONS
>> specifying `dir` will record not just a file `dir/file1`
>> modified in the working tree, a file `dir/file2` added to
>> the working tree, but also a file `dir/file3` removed from
>> - the working tree. Note that older versions of Git used
>> + the working tree). Note that older versions of Git used
>
> Good.
> ...
> OK. Just to make sure (read: not an objection to the change), this
> does not affect the formatted result, right?
Answering to myself. Documentation/doc-diff seems to find only the
")" difference we see above and nothing else. After I sent my
earlier response, I finished skimming the diff and the changes all
looked OK.
Thanks, again.
next prev parent reply other threads:[~2019-01-23 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 20:16 [PATCH] doc: tidy asciidoc style Jean-Noël Avila
2019-01-23 19:36 ` Junio C Hamano
2019-01-23 19:43 ` Junio C Hamano [this message]
2019-01-23 20:43 ` Jean-Noël AVILA
2019-01-23 21:20 ` 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=xmqqfttjb1nc.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jn.avila@free.fr \
/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).