From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Whit Armstrong <armstrong.whit@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH 0/3] solaris test results
Date: Fri, 22 Feb 2008 00:42:29 -0500 [thread overview]
Message-ID: <20080222054229.GA32294@coredump.intra.peff.net> (raw)
In-Reply-To: <7vr6f5pnmz.fsf@gitster.siamese.dyndns.org>
On Thu, Feb 21, 2008 at 09:26:44PM -0800, Junio C Hamano wrote:
> Here is a possible solution.
>
> This is a fairly mechanical substitution (grepping for "git diff -u"
> and "diff -u", and replacing them with test_compare_expect.
I think this approach is reasonable (though as I suggested in my
original message, I probably would have selected something a little
easier to type, like test_cmp).
> Test scripts can be run with --no-diff-u option, to use "git
> diff -u --no-index" for comparison instead.
I thought you were against using "git diff" in the test suite for this
purpose. Using "diff -u" produces nice output in case of failure, but
even "cmp" can do the job of returning an exit code. Perhaps it makes
sense as a more robust fallback.
Perhaps the command line option should be --compare=cmp, which lets the
caller choose an appropriate fallback for their system (and which means
that you can use --compare="git diff" to make debugging more pleasant,
but confirm with --compare="cmp" before claiming breakage on the list).
But honestly, I do not care that much about this. I don't even usually
use Solaris; I happened to have access to a box, so I followed up on
Whit's bug report. It is probably not worth spending a lot of time
over-engineering a solution. I have no idea how common it is to run the
test suite on boxes without GNU diff.
-Peff
prev parent reply other threads:[~2008-02-22 5:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 23:59 [PATCH 0/3] solaris test results Jeff King
2008-02-21 0:00 ` [PATCH 1/3] git_config_*: don't assume we are parsing a config file Jeff King
2008-02-21 0:00 ` [PATCH 2/3] t3404: use configured shell instead of /bin/sh Jeff King
2008-02-23 20:13 ` Johannes Sixt
2008-02-23 20:26 ` Junio C Hamano
2008-02-23 20:34 ` Junio C Hamano
2008-02-23 21:09 ` Johannes Sixt
2008-02-23 21:15 ` Jeff King
2008-02-23 21:56 ` Junio C Hamano
2008-02-23 22:39 ` Jeff King
2008-02-23 22:46 ` Junio C Hamano
2008-02-23 22:49 ` Jeff King
2008-02-23 22:55 ` Junio C Hamano
2008-02-23 23:12 ` Jeff King
2008-02-24 0:03 ` Junio C Hamano
2008-02-24 19:40 ` Jeff King
2008-02-23 20:40 ` Jeff King
2008-02-23 20:50 ` Junio C Hamano
2008-02-23 21:12 ` Jeff King
2008-02-23 22:28 ` Jeff King
2008-02-23 22:35 ` Junio C Hamano
2008-02-23 22:44 ` Jeff King
2008-02-21 0:01 ` [PATCH 3/3] diff: fix java funcname pattern for solaris Jeff King
2008-02-21 0:34 ` [PATCH 0/3] solaris test results Junio C Hamano
2008-02-21 0:41 ` Jeff King
2008-02-22 5:26 ` Junio C Hamano
2008-02-22 5:29 ` Junio C Hamano
2008-02-22 5:42 ` Jeff King [this message]
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=20080222054229.GA32294@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=armstrong.whit@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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.