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: Sat, 07 Nov 2026 20:35:29 -0800 [thread overview]
Message-ID: <xmqq33tc6ium.fsf@gitster.g> (raw)
In-Reply-To: <20261108023730.GA1242909@coredump.intra.peff.net> (Jeff King's message of "Sat, 7 Nov 2026 21:37:30 -0500")
Jeff King <peff@peff.net> writes:
> On Thu, Nov 05, 2026 at 03:40:17PM +0000, Julia Evans via GitGitGadget wrote:
>
>> +[[name_only]]
>> `--name-only`::
>> Show only the name of each changed file in the post-image tree.
>> The file names are often encoded in UTF-8.
>> For more information see the discussion about encoding in the linkgit:git-log[1]
>> manual page.
>
> Sadly this syntax seems to work with Asciidoctor, but not Asciidoc. The
> latter doesn't create the anchors, and then xmlto complaints that the
> result doesn't validate.
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?
Perhaps I should add an entry to the BreakingChanges document (well,
I know I know I do not think it belongs there, but since we hit this
so many times already .....).
prev parent reply other threads:[~2026-11-08 4:35 UTC|newest]
Thread overview: 15+ 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-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 [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=xmqq33tc6ium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.