From: Jonathan Tan <jonathantanmy@google.com>
To: gitster@pobox.com
Cc: jonathantanmy@google.com, hanwen@google.com, chooglen@google.com,
git@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] refs: make _advance() check struct repo, not flag
Date: Thu, 16 Sep 2021 15:05:36 -0700 [thread overview]
Message-ID: <20210916220536.1107783-1-jonathantanmy@google.com> (raw)
In-Reply-To: <xmqqilz0rxpm.fsf@gitster.g>
> > Yes, the packed backend doesn't need to be a ref backend.
>
> Sorry, I do not follow. Do you mean we cannot have a version of Git
> that offers say a read-only access to the repository without any
> loose refs, with the default ref backend being the packed one?
>
> Or do you mean that we can ignore such a hypothetical use case and
> could reimplement the files backend that can also understand the
> $GIT_DIR/packed-refs file directly without "deferring to another ref
> backend which is 'packed'"?
I meant the latter - more specifically, the files backend could defer to
functions that are not necessarily inside a struct ref_storage_be.
next prev parent reply other threads:[~2021-09-16 22:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 23:23 [RFC PATCH 0/2] First steps towards iterating over submodule refs Jonathan Tan
2021-08-25 23:23 ` [RFC PATCH 1/2] refs: make _advance() check struct repo, not flag Jonathan Tan
2021-08-26 16:39 ` Han-Wen Nienhuys
2021-08-26 22:24 ` Jonathan Tan
2021-09-14 22:41 ` Glen Choo
2021-09-15 7:35 ` Han-Wen Nienhuys
2021-09-16 17:26 ` Jonathan Tan
2021-09-16 21:56 ` Junio C Hamano
2021-09-16 22:05 ` Jonathan Tan [this message]
2021-09-16 17:24 ` Jonathan Tan
2021-08-25 23:23 ` [RFC PATCH 2/2] refs: add repo paramater to _iterator_peel() Jonathan Tan
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=20210916220536.1107783-1-jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hanwen@google.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).