From: Miklos Vajna <vmiklos@frugalware.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] t7501: always use test_cmp instead of diff
Date: Wed, 10 Sep 2008 01:49:24 +0200 [thread overview]
Message-ID: <20080909234924.GN4829@genesis.frugalware.org> (raw)
In-Reply-To: <1221003666-17115-1-git-send-email-vmiklos@frugalware.org>
[-- Attachment #1: Type: text/plain, Size: 412 bytes --]
On Wed, Sep 10, 2008 at 01:41:06AM +0200, Miklos Vajna <vmiklos@frugalware.org> wrote:
> This should make the output more readable (by default using diff -u)
> when some tests fail.
Sorry for the duplication, I didn't want to send it twice. I also just
realised after sending that I forgot to rebase it again current master,
where git-rev-list is replaced by git rev-list, but I guess git am -3
handles it. ;-)
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-09-09 23:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 23:41 [PATCH] t7501: always use test_cmp instead of diff Miklos Vajna
2008-09-09 23:49 ` Miklos Vajna [this message]
2008-09-09 23:54 ` Jeff King
2008-09-10 0:02 ` Junio C Hamano
2008-09-10 17:32 ` Miklos Vajna
-- strict thread matches above, loose matches on Subject: below --
2008-09-09 23:37 Miklos Vajna
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=20080909234924.GN4829@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--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 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).