From: Teng Long <dyroneteng@gmail.com>
To: me@ttaylorr.com
Cc: git@vger.kernel.org, gitster@pobox.com, stolee@gmail.com,
Teng Long <dyroneteng@gmail.com>
Subject: Re: [PATCH] midx: fix a formatting issue in "multi-pack-index.txt"
Date: Thu, 18 Nov 2021 11:39:59 +0800 [thread overview]
Message-ID: <20211118033959.59881-1-dyroneteng@gmail.com> (raw)
In-Reply-To: <YZQngLFWlns9HyoW@nand.local>
On Mon, Tue, 16 Nov 2021 16:49:52 -0500, Taylor Blau wrote:
> That's it. ASCIIDoc doesn't treat an indented dash character as the
> beginning of a sub-list.
That's right.
> It will treat an indented asterisk as beginning
> a sub-list, but only if the rest of the list items begin with a "-".
There are some questions here.
I think the indent is not needed for bulleted list in ASCIIDOC. If we
want to write a nested bulleted list, we could just use asterisks
without any dashes like:
"
* Level 1 list item
** Level 2 list item
*** Level 3 list item
** Level 2 list item
* Level 1 list item
** Level 2 list item
* Level 1 list item
"
And the dashes are suggested only be used as the marker for the first
level because the dash doesn’t work well or a best practice for nested
lists, like (dash is as level 2):
"
* Level 1 list item
- Level 2 list item
* Level 1 list item
"
But, if you are writting a non-nested bulleted lists, use dashes works
too, like:
"
- Level 1 list item
- Level 1 list item
- Level 1 list item
"
> 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 agree with you.
The asterisks are recommanded to use I think, it displays intuitively
when writting ASCIIDOC lists (marker length = nesting level).
> Yeah, Teng's fix works just fine. So I'd be happy to see that picked up
> (with or without much additional explanation).
I found it because I'm learning about the implements about the
multi-pack-index, reverse-index and multi-pack-bitmap, very nice
feature.
Patch v2 will add more descriptions (Derrick Stolee suggested) in
commit message and will make the replacements from dashes to asterisks.
Finally, thanks Derrick Stolee and Taylor Blau for the relies.
References:
[1] https://asciidoc-py.github.io/userguide.html#_bulleted_lists
next prev parent reply other threads:[~2021-11-18 3:40 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
2021-11-18 3:39 ` Teng Long [this message]
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=20211118033959.59881-1-dyroneteng@gmail.com \
--to=dyroneteng@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.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).