git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Thomson <ethomson@edwardthomson.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: repositoryformatversion and extensions
Date: Mon, 11 Mar 2024 11:54:55 +0000	[thread overview]
Message-ID: <CA+WKDT0fAASYE_ZhSxATv2NUnYceOP-_EF1kqKNFSOWU4QdPVQ@mail.gmail.com> (raw)

While looking at worktree configuration, I realized that the
extensions.worktreeconfig configuration option was honored even when
core.repositoryformatversion was unset, or explicitly set to 0.

Re-reading the docs for repository-version, it doesn't explicitly state
that extensions _require_ repositoryformatversion >= 1, it instead
states that:

> When reading the core.repositoryformatversion variable, a git
> implementation which supports version 1 MUST also read any configuration
> keys found in the extensions section of the configuration file.

Despite that, at least one extension (objectformat) does require
core.repositoryformatversion >= 1. Though, do note that objectformat
is not mentioned in the repository-version documentation.

What other extensions require repository format version >= 1? Is
core.objectformat the outlier here?

Is there documentation on which extensions are supported at which
repository format versions?

Are there other extensions that are not documented in repository-version?

Cheers-
Ed

             reply	other threads:[~2024-03-11 11:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 11:54 Edward Thomson [this message]
2024-03-21  9:32 ` repositoryformatversion and extensions Patrick Steinhardt
2024-03-27 10:08   ` Jeff King

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=CA+WKDT0fAASYE_ZhSxATv2NUnYceOP-_EF1kqKNFSOWU4QdPVQ@mail.gmail.com \
    --to=ethomson@edwardthomson.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).