git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: <git@vger.kernel.org>
Subject: Re: [PATCH v2] docs: note that extensions.compatobjectformat is incomplete
Date: Mon, 25 Aug 2025 15:46:26 -0700	[thread overview]
Message-ID: <xmqqms7nnhod.fsf@gitster.g> (raw)
In-Reply-To: <20250825221101.611876-1-sandals@crustytoothpaste.net> (brian m. carlson's message of "Mon, 25 Aug 2025 22:11:01 +0000")

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

> diff --git a/Documentation/config/extensions.adoc b/Documentation/config/extensions.adoc
> index 9e2f321a6d..df448da813 100644
> --- a/Documentation/config/extensions.adoc
> +++ b/Documentation/config/extensions.adoc
> @@ -14,6 +14,10 @@ compatObjectFormat::
>  	compatObjectFormat.  As well as being able to use oids encoded in
>  	compatObjectFormat in addition to oids encoded with objectFormat to
>  	locally specify objects.
> ++
> +Note that the functionality enabled by this option is incomplete and subject to
> +change.  This option currently exists only to allow development and testing of
> +the underlying feature and is not designed to be enabled by end users.

Much better.  Let's further do "This option" -> "This extension", as
all the others described in this document call themselves as such.

Thanks.

  reply	other threads:[~2025-08-25 22:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-23 22:06 [PATCH] docs: note that extensions.compatobjectformat is experimental brian m. carlson
2025-08-25 17:25 ` Junio C Hamano
2025-08-25 21:25   ` brian m. carlson
2025-08-25 22:11 ` [PATCH v2] docs: note that extensions.compatobjectformat is incomplete brian m. carlson
2025-08-25 22:46   ` Junio C Hamano [this message]
2025-08-25 22:50     ` brian m. carlson
2025-08-25 23:00       ` Junio C Hamano
2025-08-25 22:50 ` [PATCH v3] " brian m. carlson

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=xmqqms7nnhod.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.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).