From: Tian Yuchen <cat@malon.dev>
To: Junio C Hamano <gitster@pobox.com>, Trieu Huynh <vikingtc4@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [GSoC PATCH] promisor-remote: fix promisor.quiet to use the correct repository
Date: Thu, 16 Apr 2026 02:03:00 +0800 [thread overview]
Message-ID: <c87f1f12-d0cc-4150-8f43-4dc9cc1fe24f@malon.dev> (raw)
In-Reply-To: <xmqqwly86s3a.fsf@gitster.g>
On 4/16/26 01:39, Junio C Hamano wrote:
>
> The discussion thread stalled at this point. Are we happy with the
> proposed changes?
>
> Thanks.
After running it a week later, the error had (surprisingly) disappeared,
and I couldn’t reproduce it no matter what I tried.
Since the code works well on everyone’s computer and on the CI tests, I
suppose I must have got it wrong earlier.
Thanks, Yuchen
next prev parent reply other threads:[~2026-04-15 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 18:30 [GSoC PATCH] promisor-remote: fix promisor.quiet to use the correct repository Trieu Huynh
2026-04-08 17:48 ` Tian Yuchen
2026-04-08 18:23 ` Junio C Hamano
2026-04-09 4:34 ` Tian Yuchen
2026-04-13 18:22 ` Trieu Huynh
2026-04-15 17:39 ` Junio C Hamano
2026-04-15 18:03 ` Tian Yuchen [this message]
2026-04-08 17:53 ` Tian Yuchen
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=c87f1f12-d0cc-4150-8f43-4dc9cc1fe24f@malon.dev \
--to=cat@malon.dev \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vikingtc4@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