git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: ps/refstorage-extension (was: What's cooking in git.git (Jan 2024, #01; Tue, 2))
Date: Wed, 3 Jan 2024 06:53:47 +0100	[thread overview]
Message-ID: <ZZT2WoJDg-Z-_N5P@tanuki> (raw)
In-Reply-To: <xmqq5y0bcjpw.fsf@gitster.g>

[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]

On Tue, Jan 02, 2024 at 05:02:35PM -0800, Junio C Hamano wrote:
[snip]
> * ps/refstorage-extension (2024-01-02) 13 commits
>  - t9500: write "extensions.refstorage" into config
>  - builtin/clone: introduce `--ref-format=` value flag
>  - builtin/init: introduce `--ref-format=` value flag
>  - builtin/rev-parse: introduce `--show-ref-format` flag
>  - t: introduce GIT_TEST_DEFAULT_REF_FORMAT envvar
>  - setup: introduce GIT_DEFAULT_REF_FORMAT envvar
>  - setup: introduce "extensions.refStorage" extension
>  - setup: set repository's formats on init
>  - setup: start tracking ref storage format
>  - refs: refactor logic to look up storage backends
>  - worktree: skip reading HEAD when repairing worktrees
>  - t: introduce DEFAULT_REPO_FORMAT prereq
>  - Merge branch 'ps/clone-into-reftable-repository' into ps/refstorage-extension
> 
>  Introduce a new extension "refstorage" so that we can mark a
>  repository that uses a non-default ref backend, like reftable.
> 
>  Will merge to 'next'?
>  source: <cover.1703833818.git.ps@pks.im>

It's ready from my point of view, but I'm happy to wait a few days for
people to come back from holidays.

Thanks!

Patrick

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-01-03  5:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03  1:02 What's cooking in git.git (Jan 2024, #01; Tue, 2) Junio C Hamano
2024-01-03  5:53 ` Patrick Steinhardt [this message]
2024-01-03  9:01 ` Jeff King
2024-01-03 16:37   ` Junio C Hamano
2024-01-05  8:59     ` Jeff King
2024-01-05 16:34       ` Junio C Hamano
2024-01-03 17:14   ` René Scharfe
2024-01-03 16:43 ` Taylor Blau
2024-01-03 18:08   ` Junio C Hamano
2024-01-13 18:35     ` SZEDER Gábor
2024-01-13 22:06       ` Taylor Blau
2024-01-13 23:41         ` SZEDER Gábor
2024-01-16 20:37           ` Taylor Blau
2024-02-25 22:59             ` SZEDER Gábor
2024-02-26 14:44               ` Taylor Blau
2024-01-13 22:51       ` SZEDER Gábor
2024-01-16 20:49         ` Taylor Blau
2024-01-16 22:45           ` Junio C Hamano
2024-01-16 23:31             ` Taylor Blau
2024-01-16 23:42               ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZZT2WoJDg-Z-_N5P@tanuki \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).