From: Michael Rappazzo <rappazzo@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, sunshine@sunshineco.com, pclouds@gmail.com,
szeder@ira.uka.de, peff@peff.net,
Michael Rappazzo <rappazzo@gmail.com>
Subject: [PATCH v2 0/2] t1500-rev-parse: re-write t1500
Date: Sat, 16 Apr 2016 12:13:48 -0400 [thread overview]
Message-ID: <1460823230-45692-1-git-send-email-rappazzo@gmail.com> (raw)
Differences between v1[1]:
- Rebased the change on master.
- Added a test-lib function `test_stdout` which is similar to `test_cmp`.
This addition is based on a patch from Jeff King[2] found the same
discussion.
- Cleaned up the use of subshells as recommended in the discussion.
[1] http://thread.gmane.org/gmane.comp.version-control.git/291087
[2] http://thread.gmane.org/gmane.comp.version-control.git/291087/focus=291475
Michael Rappazzo (2):
test-lib: add a function to compare an expection with stdout from a
command
t1500-rev-parse: rewrite each test to run in isolation
t/t1500-rev-parse.sh | 355 ++++++++++++++++++++++++++++++++++++++++--------
t/test-lib-functions.sh | 34 +++++
2 files changed, 329 insertions(+), 60 deletions(-)
--
2.8.0
next reply other threads:[~2016-04-16 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-16 16:13 Michael Rappazzo [this message]
2016-04-16 16:13 ` [PATCH v2 1/2] test-lib: add a function to compare an expection with stdout from a command Michael Rappazzo
2016-04-17 3:07 ` Eric Sunshine
2016-04-17 3:54 ` Jeff King
2016-04-17 6:36 ` Eric Sunshine
2016-04-17 6:41 ` Jeff King
2016-04-17 15:19 ` Johannes Sixt
2016-04-17 16:22 ` Eric Sunshine
2016-04-16 16:13 ` [PATCH v2 2/2] t1500-rev-parse: rewrite each test to run in isolation Michael Rappazzo
2016-04-17 5:59 ` Eric Sunshine
2016-04-17 15:05 ` Johannes Sixt
2016-04-17 9:42 ` SZEDER Gábor
2016-04-17 16:15 ` 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=1460823230-45692-1-git-send-email-rappazzo@gmail.com \
--to=rappazzo@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.com \
--cc=szeder@ira.uka.de \
/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).