From: Taylor Blau <me@ttaylorr.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: Teng Long <dyroneteng@gmail.com>, git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] midx: fix a formatting issue in "multi-pack-index.txt"
Date: Tue, 16 Nov 2021 16:49:52 -0500 [thread overview]
Message-ID: <YZQngLFWlns9HyoW@nand.local> (raw)
In-Reply-To: <4ad06bc6-4f11-d6ef-ec95-ab0e9db9c2c7@gmail.com>
On Mon, Nov 15, 2021 at 11:25:56AM -0500, Derrick Stolee wrote:
> On 11/15/2021 1:33 AM, Teng Long wrote:
> > Signed-off-by: Teng Long <dyroneteng@gmail.com>
>
> Hi Teng,
>
> Could you spend some time in your commit message explaining what
> is wrong about the characters used for bullet points here?
>
> > - - A value j referring to the jth packfile.
> > - - An offset within the jth packfile for the object.
> > + * A value j referring to the jth packfile.
> > + * An offset within the jth packfile for the object.
> > - If large offsets are required, we use another list of large
> > offsets similar to version 2 pack-indexes.
>
> Is it that the indentation isn't enough to show a sublist?
That's it. ASCIIDoc doesn't treat an indented dash character as the
beginning of a sub-list. It will treat an indented asterisk as beginning
a sub-list, but only if the rest of the list items begin with a "-".
It might just be worth converting this whole thing to use what ASCIIDoc
would probably consider to be a more standard format, i.e.:
* A list of packfile names.
* A sorted list of object IDs.
* A list of metadata for the ith object ID including:
** A value j referring to the jth packfile.
** An offset within the jth packfile for the object.
* If large offsets are required, we use another list of large
offsets similar to version 2 pack-indexes.
> I see that the HTML rendering on git-scm.com [1] does fail to show
> this sublist, and I could believe that this change would fix it (but I
> am not sure).
>
> [1] https://www.git-scm.com/docs/multi-pack-index
Yeah, Teng's fix works just fine. So I'd be happy to see that picked up
(with or without much additional explanation).
Thanks,
Taylor
next prev parent reply other threads:[~2021-11-16 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 6:33 [PATCH] midx: fix a formatting issue in "multi-pack-index.txt" Teng Long
2021-11-15 16:25 ` Derrick Stolee
2021-11-16 21:49 ` Taylor Blau [this message]
2021-11-18 3:39 ` Teng Long
2021-11-18 7:11 ` [PATCH v2 0/1] [PATCH] midx: fix a formatting issue in docs Teng Long
2021-11-18 7:11 ` [PATCH v2 1/1] midx: fix a formatting issue in "multi-pack-index.txt" Teng Long
2021-11-18 12:16 ` Derrick Stolee
2021-11-18 23:51 ` 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=YZQngLFWlns9HyoW@nand.local \
--to=me@ttaylorr.com \
--cc=dyroneteng@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=stolee@gmail.com \
/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).