From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCH 1/2] doc: git-checkout: trivial callout cleanup
Date: Mon, 24 Apr 2023 17:02:25 -0700 [thread overview]
Message-ID: <xmqq8reg96cu.fsf@gitster.g> (raw)
In-Reply-To: 644684018a766_aba29424@chronos.notmuch
Felipe Contreras <felipe.contreras@gmail.com> writes:
> No, it's for the formatting machinery.
>
> The fact that both asciidoc and asciidoctor happen to understand our quircky
> formatting in this particualr situation doesn't mean it isn't quirky.
>
> In this particular case the parsers do understand what we are trying to do,
> because we just just pepper list continuations (`+`) everywhere and it happens
> to work.
I'll stop at pointing out that the first "no" sounds much stronger
than the text that tries to substantiate it, which says that the
machinery works fine without the changes.
> This discrepancy confused Jeff in [1].
And this is a good reason to add this change for humans.
> It's simply a good practice to follow the format asciidoctor documentation:
That one I would agree with 100%.
Thanks.
next prev parent reply other threads:[~2023-04-25 0:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 7:00 [PATCH 0/2] doc: git-checkout: trivial style improvements Felipe Contreras
2023-04-18 7:00 ` [PATCH 1/2] doc: git-checkout: trivial callout cleanup Felipe Contreras
2023-04-19 19:37 ` Junio C Hamano
2023-04-24 13:28 ` Felipe Contreras
2023-04-25 0:02 ` Junio C Hamano [this message]
2023-04-25 6:10 ` Jeff King
2023-04-27 22:09 ` Felipe Contreras
2023-05-02 10:18 ` Jeff King
2023-05-02 16:05 ` Felipe Contreras
2023-05-03 6:09 ` Junio C Hamano
2023-05-03 13:46 ` Felipe Contreras
2023-05-03 17:44 ` Junio C Hamano
2023-04-27 21:30 ` Felipe Contreras
2023-04-18 7:00 ` [PATCH 2/2] doc: git-checkout: reorganize examples Felipe Contreras
2023-04-19 19:37 ` 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=xmqq8reg96cu.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--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.
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).