From: Derrick Stolee <stolee@gmail.com>
To: Teng Long <dyroneteng@gmail.com>, git@vger.kernel.org
Cc: gitster@pobox.com, me@ttaylorr.com
Subject: Re: [PATCH v2 1/1] midx: fix a formatting issue in "multi-pack-index.txt"
Date: Thu, 18 Nov 2021 07:16:32 -0500 [thread overview]
Message-ID: <072baa38-9155-f417-12fb-4a97280daa6d@gmail.com> (raw)
In-Reply-To: <9b910a44f4143c94787110a688f2b17ba4eeb0fc.1637218943.git.dyroneteng@gmail.com>
On 11/18/2021 2:11 AM, Teng Long wrote:
> There is a formatting issue in "multi-pack-index.html", corresponding
> to the nesting bulleted list of a wrong usage in "multi-pack-index.txt"
> and this commit fix the problem.
Thank you for the detailed message!
> -- 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
> +* 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.
LGTM!
Thanks,
-Stolee
next prev parent reply other threads:[~2021-11-18 12:16 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
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 [this message]
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=072baa38-9155-f417-12fb-4a97280daa6d@gmail.com \
--to=stolee@gmail.com \
--cc=dyroneteng@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.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).