From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Patrick Steinhardt <ps@pks.im>, git@vger.kernel.org
Subject: Re: [PATCH] refs: drop `ref_store`-less functions
Date: Sun, 4 Aug 2024 12:25:47 -0400 [thread overview]
Message-ID: <Zq+riymYf+oKR4Cl@nand.local> (raw)
In-Reply-To: <xmqq34nmgbs1.fsf@gitster.g>
On Fri, Aug 02, 2024 at 08:55:10AM -0700, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks.im> writes:
>
> > In c8f815c208 (refs: remove functions without ref store, 2024-05-07), we
> > have removed functions of the refs subsystem that do not take a ref
> > store as input parameter. In order to make it easier for folks to figure
> > out how to replace calls to such functions in in-flight patch series, we
> > kept their definitions around in an ifdeffed block.
>
> Thanks for not forgetting this. Will apply.
Thanks. I agree that it is a fine time to apply this now that we're on
the other side of the 2.46 tag.
Thanks,
Taylor
prev parent reply other threads:[~2024-08-04 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 5:38 [PATCH] refs: drop `ref_store`-less functions Patrick Steinhardt
2024-08-02 15:55 ` Junio C Hamano
2024-08-04 16:25 ` Taylor Blau [this message]
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=Zq+riymYf+oKR4Cl@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
/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).