From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH] RelNotes: update the v0 with extension situation
Date: Fri, 17 Jul 2020 13:51:33 -0700 [thread overview]
Message-ID: <xmqqk0z1dfvu.fsf@gitster.c.googlers.com> (raw)
With the two-patch series for regression fix, to the users from 2.27
days, there is no visible behaviour change---we do not warn and fail
use of v0 repositories with newer extensions yet, so there is nothing
to note in the backward compatibility section.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
* I noticed that this was needed but unfortunately not before
tagging and tarballing.
Documentation/RelNotes/2.28.0.txt | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/Documentation/RelNotes/2.28.0.txt b/Documentation/RelNotes/2.28.0.txt
index 934f5e652b..da9cafb788 100644
--- a/Documentation/RelNotes/2.28.0.txt
+++ b/Documentation/RelNotes/2.28.0.txt
@@ -9,15 +9,6 @@ Backward compatibility notes
* "fetch.writeCommitGraph" is deemed to be still a bit too risky and
is no longer part of the "feature.experimental" set.
- * It used to be that setting extensions.* configuration variables
- alone, while leaving core.repositoryFormatVersion=0, made these
- settings effective, which was a wrong thing to do. In version 0,
- there was no special meaning in extensions.* configuration
- variables. This has been corrected. If you need these repository
- extensions to be effective, the core.repositoryFormatVersion
- variable needs to be updated to 1 after vetting these extensions.*
- variables are set correctly.
-
UI, Workflows & Features
--
2.28.0-rc1
reply other threads:[~2020-07-17 20:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=xmqqk0z1dfvu.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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).