From: Jialong Wang <jerrywang183@yahoo•com>
To: gitster@pobox•com
Cc: git@vger•kernel.org
Subject: Re: [GSoC PATCH] t2203: avoid suppressing git status exit code
Date: Tue, 17 Mar 2026 15:25:25 -0400 [thread overview]
Message-ID: <177377552540.75212.11758229294443511273@yahoo.com> (raw)
In-Reply-To: <xmqqmse3fsvw.fsf@gitster.g>
Hi Junio,
Thanks, that was my mistake.
I resent it with the GSoC subject prefix, but I should have treated it
as a new version of the earlier patch, sent as [GSoC PATCH v2] in
reply to the original thread, with a short note about what changed.
I'll do that for future rerolls.
Thanks,
Jialong
next parent reply other threads:[~2026-03-17 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260317185414.65952-1-jerrywang183@yahoo.com>
[not found] ` <xmqqmse3fsvw.fsf@gitster.g>
2026-03-17 19:25 ` Jialong Wang [this message]
[not found] <20260317185048.74421-1-jerrywang183.ref@yahoo.com>
2026-03-17 18:50 ` [GSoC PATCH] t2203: avoid suppressing git status exit code Jialong Wang
2026-03-17 19:01 ` Junio C Hamano
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=177377552540.75212.11758229294443511273@yahoo.com \
--to=jerrywang183@yahoo$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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