From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Julia Evans via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, "D. Ben Knoble" <ben.knoble@gmail.com>,
Julia Evans <julia@jvns.ca>
Subject: Re: [PATCH v2] doc: git-diff: rewrite EXAMPLES section
Date: Mon, 09 Nov 2026 12:31:06 -0800 [thread overview]
Message-ID: <xmqqh5hpycfp.fsf@gitster.g> (raw)
In-Reply-To: <20261109185301.GB1322417@coredump.intra.peff.net> (Jeff King's message of "Mon, 9 Nov 2026 13:53:01 -0500")
Jeff King <peff@peff.net> writes:
> On Sat, Nov 07, 2026 at 08:35:29PM -0800, Junio C Hamano wrote:
>
>> An offtopic tangent but didn't we repeatedly float ideas to drop
>> support for AsciiDoc, make sure our documentation set renders well
>> only with AsciiDoctor, and tell folks who do not use AsciiDoctor to
>> use pre-rendered documentation pages from git-htmldocs.git and
>> git-manpages.git repositories at https://git.kernel.org/pub/scm/git/
>> during the past several months?
>
> Yeah, that's what I was hinting at near the bottom of my message. :)
>
> But it's a big enough change that this series should probably just
> accept the ugly syntax for now, rather than waiting for us to drop
> python asciidoc support.
Yup, agreed. Improvements for these examples do not have to be held
hostage on the toolchain support.
next prev parent reply other threads:[~2026-11-09 20:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 15:33 [PATCH] doc: git-diff: rewrite EXAMPLES section Julia Evans via GitGitGadget
2026-11-03 17:16 ` Julia Evans
2026-11-03 19:44 ` Junio C Hamano
2026-11-03 19:52 ` Julia Evans
2026-11-03 20:33 ` Junio C Hamano
2026-11-03 20:45 ` Julia Evans
2026-11-03 21:42 ` Junio C Hamano
2026-11-05 15:40 ` [PATCH v2] " Julia Evans via GitGitGadget
2026-11-05 16:46 ` Junio C Hamano
2026-11-05 18:18 ` Junio C Hamano
2026-11-09 12:48 ` D. Ben Knoble
2026-11-10 13:43 ` Julia Evans
2026-11-05 17:23 ` Tuomas Ahola
2026-11-05 19:45 ` Junio C Hamano
2026-11-05 19:46 ` Junio C Hamano
2026-11-08 2:37 ` Jeff King
2026-11-08 4:35 ` Junio C Hamano
2026-11-09 18:53 ` Jeff King
2026-11-09 20:31 ` Junio C Hamano [this message]
2026-11-09 22:20 ` Junio C Hamano
2026-11-09 22:40 ` Junio C Hamano
2026-11-09 23:09 ` Jeff King
2026-11-10 13:46 ` Julia Evans
2026-11-10 15:25 ` Kaartic Sivaraam
2026-11-11 20:17 ` Julia Evans
2026-11-10 17:22 ` Junio C Hamano
2026-11-11 20:13 ` [PATCH v3] " Julia Evans via GitGitGadget
2026-11-11 21:52 ` 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=xmqqh5hpycfp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=julia@jvns.ca \
--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