git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org,  Jeff King <peff@peff.net>
Subject: Re: [PATCH] Documentation/config/pack.txt: fix broken AsciiDoc
Date: Fri, 23 Feb 2024 14:15:16 -0800	[thread overview]
Message-ID: <xmqqr0h2su8b.fsf@gitster.g> (raw)
In-Reply-To: <72bb58e5f3b8a5a622394c5ff40426156e122580.1708720255.git.me@ttaylorr.com> (Taylor Blau's message of "Fri, 23 Feb 2024 15:30:58 -0500")

Taylor Blau <me@ttaylorr.com> writes:

> diff --git a/Documentation/config/pack.txt b/Documentation/config/pack.txt
> index 9c630863e6..da527377fa 100644
> --- a/Documentation/config/pack.txt
> +++ b/Documentation/config/pack.txt
> @@ -34,11 +34,10 @@ pack.allowPackReuse::
>  	reachability bitmap is available, pack-objects will try to send
>  	parts of all packs in the MIDX.
>  +
> -	If only a single pack bitmap is available, and
> -	`pack.allowPackReuse` is set to "multi", reuse parts of just the
> -	bitmapped packfile. This can reduce memory and CPU usage to
> -	serve fetches, but might result in sending a slightly larger
> -	pack. Defaults to true.
> +If only a single pack bitmap is available, and `pack.allowPackReuse`
> +is set to "multi", reuse parts of just the bitmapped packfile. This
> +can reduce memory and CPU usage to serve fetches, but might result in
> +sending a slightly larger pack. Defaults to true.

Thanks.

      reply	other threads:[~2024-02-23 22:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 20:30 [PATCH] Documentation/config/pack.txt: fix broken AsciiDoc Taylor Blau
2024-02-23 22:15 ` 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=xmqqr0h2su8b.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.com \
    --cc=peff@peff.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;
as well as URLs for NNTP newsgroup(s).