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: fix misleading asciidoc formating
Date: Wed, 06 Mar 2019 07:39:52 +0900 [thread overview]
Message-ID: <xmqqd0n5t07b.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20190305214423.27820-1-jn.avila@free.fr> ("Jean-Noël Avila"'s message of "Tue, 5 Mar 2019 22:44:23 +0100")
Jean-Noël Avila <jn.avila@free.fr> writes:
> The end of sentence in "x." at the begining of a line misleads
> ascidoctor into interpreting it as the start of numbered sub-list.
Wow. That's tricky.
One thing that makes me wonder is how you found it, as I do not
think this file is part of the set of Documentation/technical/ files
that are usually touched by "make doc".
> Signed-off-by: Jean-Noël Avila <jn.avila@free.fr>
> ---
> Documentation/technical/directory-rename-detection.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/technical/directory-rename-detection.txt b/Documentation/technical/directory-rename-detection.txt
> index 1c0086e287..844629c8c4 100644
> --- a/Documentation/technical/directory-rename-detection.txt
> +++ b/Documentation/technical/directory-rename-detection.txt
> @@ -20,8 +20,8 @@ More interesting possibilities exist, though, such as:
> * one side of history renames x -> z, and the other renames some file to
> x/e, causing the need for the merge to do a transitive rename.
>
> - * one side of history renames x -> z, but also renames all files within
> - x. For example, x/a -> z/alpha, x/b -> z/bravo, etc.
> + * one side of history renames x -> z, but also renames all files within x.
> + For example, x/a -> z/alpha, x/b -> z/bravo, etc.
>
> * both 'x' and 'y' being merged into a single directory 'z', with a
> directory rename being detected for both x->z and y->z.
prev parent reply other threads:[~2019-03-05 22:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 21:44 [PATCH] Doc: fix misleading asciidoc formating Jean-Noël Avila
2019-03-05 22:36 ` Jeff King
2019-03-05 22:54 ` Junio C Hamano
2019-03-05 23:02 ` Jeff King
2019-03-05 23:11 ` Jeff King
2019-03-05 23:44 ` Junio C Hamano
2019-03-06 8:07 ` Jean-Noël Avila
2019-03-06 19:06 ` Jeff King
2019-03-06 23:39 ` Junio C Hamano
2019-03-05 22:39 ` Junio C Hamano [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqd0n5t07b.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).