From: Junio C Hamano <gitster@pobox.com>
To: Robert Coup <robert.coup@koordinates.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2023, #09; Mon, 30)
Date: Tue, 31 Oct 2023 05:59:38 +0900 [thread overview]
Message-ID: <xmqqttq7ddxh.fsf@gitster.g> (raw)
In-Reply-To: <CAFLLRpJCPxRMJEs5GxNuqmANn+DpuSAfGb9C94qvPuPNDdaWsA@mail.gmail.com> (Robert Coup's message of "Mon, 30 Oct 2023 09:31:36 +0000")
Robert Coup <robert.coup@koordinates.com> writes:
> Any thoughts on picking up "upload-pack: add tracing for fetches" [1]?
> It received positive feedback from Taylor and Peff, and I submitted a
> v2 [2] addressing the comments that Peff has re-reviewed.
Thanks for pinging. It slipped through the cracks.
Queued.
prev parent reply other threads:[~2023-10-30 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 23:52 What's cooking in git.git (Oct 2023, #09; Mon, 30) Junio C Hamano
2023-10-30 9:31 ` Robert Coup
2023-10-30 20:59 ` 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=xmqqttq7ddxh.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=robert.coup@koordinates.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 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.