From: Junio C Hamano <gitster@pobox.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: git@vger.kernel.org, Derrick Stolee <dstolee@microsoft.com>
Subject: Re: [PATCH] multi-pack-index: correct configuration in documentation
Date: Sat, 04 Jan 2020 15:03:08 -0800 [thread overview]
Message-ID: <xmqqr20ebz9v.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20200104124314.10134-1-johannes@sipsolutions.net> (Johannes Berg's message of "Sat, 4 Jan 2020 13:43:14 +0100")
Johannes Berg <johannes@sipsolutions.net> writes:
> It's core.multiPackIndex, not pack.multiIndex.
>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
> ---
> Documentation/technical/multi-pack-index.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks, will queue.
> diff --git a/Documentation/technical/multi-pack-index.txt b/Documentation/technical/multi-pack-index.txt
> index 1e312396966c..4e7631437a58 100644
> --- a/Documentation/technical/multi-pack-index.txt
> +++ b/Documentation/technical/multi-pack-index.txt
> @@ -36,7 +36,7 @@ Design Details
> directory of an alternate. It refers only to packfiles in that
> same directory.
>
> -- The pack.multiIndex config setting must be on to consume MIDX files.
> +- The core.multiPackIndex config setting must be on to consume MIDX files.
>
> - The file format includes parameters for the object ID hash
> function, so a future change of hash algorithm does not require
prev parent reply other threads:[~2020-01-04 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 12:43 [PATCH] multi-pack-index: correct configuration in documentation Johannes Berg
2020-01-04 23:03 ` 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=xmqqr20ebz9v.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=johannes@sipsolutions.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox