From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Stephan Beyer <s-beyer@gmx.net>
Cc: git@vger.kernel.org
Subject: Re: [HACK] t/test-lib.sh HACK: Add -s/--show-hack to test suite.
Date: Sun, 13 Jul 2008 02:25:22 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.1.00.0807130222320.2995@eeepc-johanness> (raw)
In-Reply-To: <20080712222212.GC22323@leksak.fem-net>
Hi,
On Sun, 13 Jul 2008, Stephan Beyer wrote:
> Johannes Schindelin wrote:
>
> > On Mon, 7 Jul 2008, Stephan Beyer wrote:
> >
> > > > > This option realizes a stupid hack that tries to run the test
> > > > > cases line by line (separated by &&).
> > > >
> > > > In what way is that better than "sh -x t????-*.sh"?
> > >
> > > Your suggestion is more like "./t????-*.sh -v" instead of -s, at
> > > least on bash and dash here.
> >
> > No, I meant without "-v".
>
> Me, too.
>
> I've written something different: "sh -x" is a great thing and does
> exactly what it should on simple scripts containing:
>
> foo &&
> bar &&
> baz
>
> But for a test case in the git test suite it does not work, unfortunately.
Huh?
When I run "sh -x t*.sh", it lists _every_ command that was executed in
the script, and even more: it shows me the result, too! If there was a
function that was called, it prefixes an additional "+" so that I can
follow recursion better.
All in all, "sh -x" is a very versatile tool.
As far as I undertood your commit message, your HACK would have done the
first part: list what commands were executed. This is less than what "sh
-x" does.
Please clarify,
Dscho
next prev parent reply other threads:[~2008-07-13 0:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 20:22 [HACK] t/test-lib.sh HACK: Add -s/--show-hack to test suite Stephan Beyer
2008-07-06 20:41 ` Johannes Schindelin
2008-07-07 14:08 ` Stephan Beyer
2008-07-07 14:41 ` Johannes Schindelin
2008-07-12 22:22 ` Stephan Beyer
2008-07-13 0:25 ` Johannes Schindelin [this message]
2008-07-13 11:09 ` Stephan Beyer
2008-07-13 13:21 ` Johannes Schindelin
2008-07-21 1:24 ` Stephan Beyer
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.00.0807130222320.2995@eeepc-johanness \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=s-beyer@gmx.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).