All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Alex Henrie <alexhenrie24@gmail.com>
Cc: git@vger.kernel.org, chakrabortyabhradeep79@gmail.com,
	me@ttaylorr.com, kaartic.sivaraam@gmail.com
Subject: Re: [PATCH] pack-bitmap: improve grammar of "xor chain" error message
Date: Fri, 23 Sep 2022 08:55:24 -0700	[thread overview]
Message-ID: <xmqqv8pew0er.fsf@gitster.g> (raw)
In-Reply-To: <20220922025158.415969-1-alexhenrie24@gmail.com> (Alex Henrie's message of "Wed, 21 Sep 2022 20:51:58 -0600")

Alex Henrie <alexhenrie24@gmail.com> writes:

> Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
> ---
>  pack-bitmap.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/pack-bitmap.c b/pack-bitmap.c
> index 9a208abc1f..9d5205055a 100644
> --- a/pack-bitmap.c
> +++ b/pack-bitmap.c
> @@ -723,7 +723,7 @@ static struct stored_bitmap *lazy_bitmap_for_commit(struct bitmap_index *bitmap_
>  		ALLOC_GROW(xor_items, xor_items_nr + 1, xor_items_alloc);
>  
>  		if (xor_items_nr + 1 >= bitmap_git->entry_count) {
> -			error(_("corrupt bitmap lookup table: xor chain exceed entry count"));
> +			error(_("corrupt bitmap lookup table: xor chain exceeds entry count"));

Thanks.  This will affect the l10n team, and the change is obviously
innocuous, so let's merge it down immediately to the 'master' branch
to make the life of l10n team more predictable.


      reply	other threads:[~2022-09-23 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22  2:51 [PATCH] pack-bitmap: improve grammar of "xor chain" error message Alex Henrie
2022-09-23 15:55 ` 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=xmqqv8pew0er.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=alexhenrie24@gmail.com \
    --cc=chakrabortyabhradeep79@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.