From: Edwin Fernando <edwinfernando734@gmail.com>
To: git@vger.kernel.org
Cc: vdye@github.org, Edwin Fernando <edwinfernando734@gmail.com>
Subject: [GSOC][PATCH 0/1] Avoid suppression of git's exit code in tests
Date: Sun, 26 Mar 2023 18:31:46 +0100 [thread overview]
Message-ID: <20230326173147.39626-1-edwinfernando734@gmail.com> (raw)
This is a GSOC microproject. Address the problem of errors resulting
from calling git in the test scripts being suppressed. Suppressions
due to pipes and command substitution were encountered in this
file (t/t3701). These regexs where used to search for such occurences
.*\<git\>.*|.* and .*$(.*git.*).* respectively (in vim).
Both types have been resolved and the tests pass as before commit.
Edwin Fernando (1):
t3701: Avoid suppression of exit status of git
t/t3701-add-interactive.sh | 25 ++++++++++++++++---------
1 file changed, 16 insertions(+), 9 deletions(-)
base-commit: d15644fe0226af7ffc874572d968598564a230dd
--
2.40.0
next reply other threads:[~2023-03-26 17:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 17:31 Edwin Fernando [this message]
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
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=20230326173147.39626-1-edwinfernando734@gmail.com \
--to=edwinfernando734@gmail.com \
--cc=git@vger.kernel.org \
--cc=vdye@github.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.