From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 8/9] Use git diff instead of diff in t7201
Date: Fri, 25 Jan 2008 15:57:50 -0800 [thread overview]
Message-ID: <7v1w855ugx.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0801251824010.13593@iabervon.org> (Daniel Barkalow's message of "Fri, 25 Jan 2008 18:25:07 -0500 (EST)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> If the test failed, it was giving really unclear ed script
> output. Instead, give a diff that sort of suggests the problem.
Hmm. I'd actually prefer using "diff -u" instead.
next prev parent reply other threads:[~2008-01-25 23:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 23:25 [PATCH 8/9] Use git diff instead of diff in t7201 Daniel Barkalow
2008-01-25 23:57 ` Junio C Hamano [this message]
2008-01-26 0:11 ` Daniel Barkalow
-- strict thread matches above, loose matches on Subject: below --
2008-02-04 18:36 Daniel Barkalow
2008-02-05 1:40 ` Johannes Schindelin
2008-02-05 20:39 ` Daniel Barkalow
2008-02-05 23:44 ` Junio C Hamano
2008-02-06 1:13 ` Daniel Barkalow
2008-02-06 2:10 ` Junio C Hamano
2008-02-06 4:30 ` Daniel Barkalow
2008-02-06 5:21 ` Junio C Hamano
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=7v1w855ugx.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.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 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).