From: Junio C Hamano <gitster@pobox.com>
To: Eric Wong <e@80x24.org>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2023, #05; Fri, 24)
Date: Mon, 27 Feb 2023 11:00:35 -0800 [thread overview]
Message-ID: <xmqq356rszl8.fsf@gitster.g> (raw)
In-Reply-To: <xmqqa60zszq9.fsf@gitster.g> (Junio C. Hamano's message of "Mon, 27 Feb 2023 10:57:34 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Eric Wong <e@80x24.org> writes:
>
>> Junio C Hamano <gitster@pobox.com> wrote:
>>> [New Topics]
>>
>> Any feedback for <20230212090426.M558990@dcvr>?
>> ([PATCH v2] fetch: support hideRefs to speed up connectivity checks)
>
> Ah, that one slipped through the cracks, it seems.
>
> Thanks for pinging; queued.
Ah, sorry, you were asking for "feedback". I think relative to the
original RFC I think what you have is an improvement. It does make
me wonder if we want to later add 'push' to the family to complete
the client-server for both directions, but that is irrelevant in
evaluating this change.
Thanks.
prev parent reply other threads:[~2023-02-27 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 20:24 What's cooking in git.git (Feb 2023, #05; Fri, 24) Junio C Hamano
2023-02-26 8:15 ` Eric Wong
2023-02-27 18:57 ` Junio C Hamano
2023-02-27 19:00 ` Junio C Hamano [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=xmqq356rszl8.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=e@80x24.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.