From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jean-Noël Avila" <jn.avila@free.fr>, git@vger.kernel.org
Subject: Re: [PATCH] Doc: fix misleading asciidoc formating
Date: Tue, 5 Mar 2019 18:11:42 -0500 [thread overview]
Message-ID: <20190305231142.GA359@sigill.intra.peff.net> (raw)
In-Reply-To: <20190305230227.GA22901@sigill.intra.peff.net>
On Tue, Mar 05, 2019 at 06:02:27PM -0500, Jeff King wrote:
> On Wed, Mar 06, 2019 at 07:54:20AM +0900, Junio C Hamano wrote:
>
> > Jeff King <peff@peff.net> writes:
> >
> > > Did you notice this when building locally, or on the asciidoctor-built
> > > pages at git-scm.com?
> >
> > Does git-scm.com even have this file rendered? I do not think we
> > glob for technical/*.txt in any of our Makefiles; instead we have a
> > list of ready-to-be-consumed TECH_DOCS listed explicitly.
>
> It is rendered, at https://git-scm.com/docs/directory-rename-detection.
By the way, that rendering shows that the whole document could probably
use a few tweaks to make its asciidoc formatting look good (in addition
to the "x." thing that Jean-Noël fixed here, which can also be seen
there).
TBH, I still have mixed feelings on rendering these technical docs with
asciidoc at all. It seems like few enough people bother to render them
that bugs persist for a long time. It kind of seems like make-work
getting them to format correctly.
-Peff
next prev parent reply other threads:[~2019-03-05 23:11 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 [this message]
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
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=20190305231142.GA359@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).