From: Edwin Fernando <edwinfernando734@gmail.com>
To: sunshine@sunshineco.com
Cc: edwinfernando734@gmail.com, git@vger.kernel.org, rybak.a.v@gmail.com
Subject: Re: [GSOC][PATCH v4] t3701: don't lose "git" exit codes in test scripts
Date: Mon, 3 Apr 2023 10:21:30 +0100 [thread overview]
Message-ID: <20230403092130.40900-1-edwinfernando734@gmail.com> (raw)
In-Reply-To: <CAPig+cTq9mmLGmmNWQ0E73nsmwu+Lj1jDfvnniUe-O6iQrisnw@mail.gmail.com>
next prev parent reply other threads:[~2023-04-03 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 17:31 [GSOC][PATCH 0/1] Avoid suppression of git's exit code in tests Edwin Fernando
2023-03-26 17:31 ` [GSOC][PATCH 1/1] t3701: Avoid suppression of exit status of git Edwin Fernando
2023-03-26 20:14 ` Andrei Rybak
2023-03-27 10:11 ` Eric Sunshine
2023-04-01 19:47 ` [GSOC][PATCH v2] t3701: don't lose "git" exit codes in test scripts Edwin Fernando
2023-04-02 10:41 ` Andrei Rybak
2023-04-02 11:36 ` [GSOC][PATCH v3] " Edwin Fernando
2023-04-02 17:17 ` Eric Sunshine
2023-04-02 19:17 ` [GSOC][PATCH v4] " Edwin Fernando
2023-04-03 6:24 ` Eric Sunshine
2023-04-03 9:21 ` Edwin Fernando [this message]
2023-04-03 9:34 ` Edwin Fernando
2023-04-03 17:03 ` Eric Sunshine
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=20230403092130.40900-1-edwinfernando734@gmail.com \
--to=edwinfernando734@gmail.com \
--cc=git@vger.kernel.org \
--cc=rybak.a.v@gmail.com \
--cc=sunshine@sunshineco.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;
as well as URLs for NNTP newsgroup(s).