All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Bence Ferdinandy <bence@ferdinandy.com>
Cc: git@vger.kernel.org,  Patrick Steinhardt <ps@pks.im>
Subject: Re: [PATCH] t/README: add missing value for GIT_TEST_DEFAULT_REF_FORMAT
Date: Fri, 11 Oct 2024 14:18:49 -0700	[thread overview]
Message-ID: <xmqqjzeecp8m.fsf@gitster.g> (raw)
In-Reply-To: <20241011191150.825255-1-bence@ferdinandy.com> (Bence Ferdinandy's message of "Fri, 11 Oct 2024 21:11:33 +0200")

Bence Ferdinandy <bence@ferdinandy.com> writes:

> The documentation only lists "files" as a possible value, but
> "reftable" is also valid.

Makes sense.  Will queue.  Thanks.

>
> Signed-off-by: Bence Ferdinandy <bence@ferdinandy.com>
> ---
>  t/README | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/t/README b/t/README
> index 8dcb778e26..8c0319b58e 100644
> --- a/t/README
> +++ b/t/README
> @@ -465,8 +465,9 @@ GIT_TEST_DEFAULT_HASH=<hash-algo> specifies which hash algorithm to
>  use in the test scripts. Recognized values for <hash-algo> are "sha1"
>  and "sha256".
>  
> -GIT_TEST_DEFAULT_REF_FORMAT=<format> specifies which ref storage format
> -to use in the test scripts. Recognized values for <format> are "files".
> +GIT_TEST_DEFAULT_REF_FORMAT=<format> specifies which ref storage format to use
> +in the test scripts. Recognized values for <format> are "files" and
> +"reftable".
>  
>  GIT_TEST_NO_WRITE_REV_INDEX=<boolean>, when true disables the
>  'pack.writeReverseIndex' setting.

  reply	other threads:[~2024-10-11 21:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11 19:11 [PATCH] t/README: add missing value for GIT_TEST_DEFAULT_REF_FORMAT Bence Ferdinandy
2024-10-11 21:18 ` Junio C Hamano [this message]
2024-10-12  8:32   ` Patrick Steinhardt

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=xmqqjzeecp8m.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=bence@ferdinandy.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    /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.