git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: karthik nayak <karthik.188@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 04/10] refs/files: support symbolic and root refs in initial transaction
Date: Mon, 11 Nov 2024 13:53:09 +0100	[thread overview]
Message-ID: <ZzH-NTDJlUH48vRM@pks.im> (raw)
In-Reply-To: <CAOLa=ZSKH_OY5XG+toFUT2fD+6c7fshNZDfcOOSydxH23D91Zg@mail.gmail.com>

On Mon, Nov 11, 2024 at 02:42:11AM -0800, karthik nayak wrote:
> Patrick Steinhardt <ps@pks.im> writes:
> 
> > The "files" backend has implemented special logic when committing
> > the first transactions in an otherwise empty ref store: instead of
> > writing all refs as separate loose files, it instead knows to write them
> > all into a "packed-refs" file directly. This is significantly more
> > efficient than having to write each of the refs as separate "loose" ref.
> >
> > The only user of this optimization is git-clone(1), which only uses this
> > mechanism to write regular refs. Consequently, the implementation does
> > not know how to handle both symbolic and root refs. While fine in the
> > context of git-clone(1), this keeps us from using the mechanism in more
> > cases.
> >
> > Adapt the logic to also support symbolic and root refs by using a second
> > transaction that we use for all of the refs that need to be written as
> > loose refs.
> >
> 
> The patch looks good. I was wondering if another way would be to just
> add symref and root ref support to packed-refs. But that might be a
> bigger undertaking than what we're doing here.
> 
> But thinking about it, seems like we can do that in a backwards
> compatible way too.

I don't think you can without introducing a new version of the format,
mostly because you also have to think about clients that don't support
the new format. So all of this would be a big undertaking, and given
that we have the reftable backend nowadays I don't think it'd be all
that valuable.

Patrick

  reply	other threads:[~2024-11-11 12:53 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08  9:34 [PATCH 00/10] refs: optimize ref format migrations Patrick Steinhardt
2024-11-08  9:34 ` [PATCH 01/10] refs: allow passing flags when setting up a transaction Patrick Steinhardt
2024-11-11 10:30   ` karthik nayak
2024-11-11 12:53     ` Patrick Steinhardt
2024-11-08  9:34 ` [PATCH 02/10] refs/files: move logic to commit initial transaction Patrick Steinhardt
2024-11-08  9:34 ` [PATCH 03/10] refs: introduce "initial" transaction flag Patrick Steinhardt
2024-11-08  9:34 ` [PATCH 04/10] refs/files: support symbolic and root refs in initial transaction Patrick Steinhardt
2024-11-11 10:42   ` karthik nayak
2024-11-11 12:53     ` Patrick Steinhardt [this message]
2024-11-08  9:34 ` [PATCH 05/10] refs: use "initial" transaction semantics to migrate refs Patrick Steinhardt
2024-11-11 10:43   ` karthik nayak
2024-11-08  9:34 ` [PATCH 06/10] refs: skip collision checks in initial transactions Patrick Steinhardt
2024-11-11 10:53   ` karthik nayak
2024-11-08  9:34 ` [PATCH 07/10] refs: don't normalize log messages with `REF_SKIP_CREATE_REFLOG` Patrick Steinhardt
2024-11-08  9:34 ` [PATCH 08/10] reftable/writer: optimize allocations by using a scratch buffer Patrick Steinhardt
2024-11-08  9:34 ` [PATCH 09/10] reftable/block: rename `block_writer::buf` variable Patrick Steinhardt
2024-11-08  9:34 ` [PATCH 10/10] reftable/block: optimize allocations by using scratch buffer Patrick Steinhardt
2024-11-11 10:57 ` [PATCH 00/10] refs: optimize ref format migrations karthik nayak
2024-11-11 12:53   ` Patrick Steinhardt
2024-11-20  7:04     ` Junio C Hamano
2024-11-20  7:50       ` Patrick Steinhardt
2024-11-20 10:25         ` Christian Couder
2024-11-25  5:52           ` Patrick Steinhardt
2024-11-20  7:51 ` [PATCH v2 " Patrick Steinhardt
2024-11-20  7:51   ` [PATCH v2 01/10] refs: allow passing flags when setting up a transaction Patrick Steinhardt
2024-11-20 10:19     ` Christian Couder
2024-11-20  7:51   ` [PATCH v2 02/10] refs/files: move logic to commit initial transaction Patrick Steinhardt
2024-11-20  7:51   ` [PATCH v2 03/10] refs: introduce "initial" transaction flag Patrick Steinhardt
2024-11-20  7:51   ` [PATCH v2 04/10] refs/files: support symbolic and root refs in initial transaction Patrick Steinhardt
2024-11-20  7:51   ` [PATCH v2 05/10] refs: use "initial" transaction semantics to migrate refs Patrick Steinhardt
2024-11-20  7:51   ` [PATCH v2 06/10] refs: skip collision checks in initial transactions Patrick Steinhardt
2024-11-20 10:21     ` Christian Couder
2024-11-25  5:52       ` Patrick Steinhardt
2024-11-20 10:42     ` Kristoffer Haugsbakk
2024-11-25  5:52       ` Patrick Steinhardt
2024-11-20  7:51   ` [PATCH v2 07/10] refs: don't normalize log messages with `REF_SKIP_CREATE_REFLOG` Patrick Steinhardt
2024-11-20  7:51   ` [PATCH v2 08/10] reftable/writer: optimize allocations by using a scratch buffer Patrick Steinhardt
2024-11-20 10:21     ` Christian Couder
2024-11-25  5:52       ` Patrick Steinhardt
2024-11-20  7:51   ` [PATCH v2 09/10] reftable/block: rename `block_writer::buf` variable Patrick Steinhardt
2024-11-20  7:51   ` [PATCH v2 10/10] reftable/block: optimize allocations by using scratch buffer Patrick Steinhardt
2024-11-20 10:22     ` Christian Couder
2024-11-25  6:27 ` [PATCH v3 00/10] refs: optimize ref format migrations Patrick Steinhardt
2024-11-25  6:27   ` [PATCH v3 01/10] refs: allow passing flags when setting up a transaction Patrick Steinhardt
2024-11-25  6:27   ` [PATCH v3 02/10] refs/files: move logic to commit initial transaction Patrick Steinhardt
2024-11-25  6:27   ` [PATCH v3 03/10] refs: introduce "initial" transaction flag Patrick Steinhardt
2024-11-25  6:27   ` [PATCH v3 04/10] refs/files: support symbolic and root refs in initial transaction Patrick Steinhardt
2024-11-25  6:27   ` [PATCH v3 05/10] refs: use "initial" transaction semantics to migrate refs Patrick Steinhardt
2024-11-25  6:27   ` [PATCH v3 06/10] refs: skip collision checks in initial transactions Patrick Steinhardt
2024-11-25  6:27   ` [PATCH v3 07/10] refs: don't normalize log messages with `REF_SKIP_CREATE_REFLOG` Patrick Steinhardt
2024-11-25  6:27   ` [PATCH v3 08/10] reftable/writer: optimize allocations by using a scratch buffer Patrick Steinhardt
2024-11-25  6:27   ` [PATCH v3 09/10] reftable/block: rename `block_writer::buf` variable Patrick Steinhardt
2024-11-25  6:27   ` [PATCH v3 10/10] reftable/block: optimize allocations by using scratch buffer Patrick Steinhardt
2024-11-25  6:29   ` [PATCH v3 00/10] refs: optimize ref format migrations Patrick Steinhardt

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=ZzH-NTDJlUH48vRM@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=karthik.188@gmail.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.
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).