From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>, git@vger.kernel.org
Subject: Re: [PATCH] docs: correct information about reftable
Date: Wed, 08 Apr 2026 07:20:12 -0700 [thread overview]
Message-ID: <xmqqy0ix1qlf.fsf@gitster.g> (raw)
In-Reply-To: <adX65j-4Vb24GpF8@pks.im> (Patrick Steinhardt's message of "Wed, 8 Apr 2026 08:51:18 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> On Thu, Apr 02, 2026 at 10:42:41PM +0000, brian m. carlson wrote:
>> Our description of the reftable format is that it is experimental and
>> subject to change, but that is no longer true. Remove this statement so
>> as not to mislead users.
>>
>> In addition, the documentation says that the files format is the
>> default, but that is not true if breaking changes mode is on. Correct
>> this information with a conditional.
>
> Makes sense to me, thanks!
>
> Patrick
Thanks for this ack---the patch message somehow escaped from my
radar. Will apply.
prev parent reply other threads:[~2026-04-08 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 22:42 [PATCH] docs: correct information about reftable brian m. carlson
2026-04-08 6:51 ` Patrick Steinhardt
2026-04-08 14:20 ` 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=xmqqy0ix1qlf.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
--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