git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Brian Gernhardt <brian@gernhardtsoftware.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Charles Bailey <charles@hashpling.org>
Subject: Re: t7610-mergetool.sh -q isn't quiet
Date: Fri, 20 Aug 2010 21:03:01 +0000	[thread overview]
Message-ID: <AANLkTink1HaOWCYsr5+Q+JAi_zA_gEHmOU1J3fvq8jnd@mail.gmail.com> (raw)
In-Reply-To: <E395511F-ACF9-4390-A081-4AC4C072C7CC@gernhardtsoftware.com>

On Fri, Aug 20, 2010 at 06:50, Brian Gernhardt
<brian@gernhardtsoftware.com> wrote:

>    test "$(cat ../file1)" = "master updated" &&
>    test "$(cat ../file2)" = "master new" &&

That should also use test_cmp.

      reply	other threads:[~2010-08-20 21:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-20  6:50 t7610-mergetool.sh -q isn't quiet Brian Gernhardt
2010-08-20 21:03 ` Ævar Arnfjörð Bjarmason [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=AANLkTink1HaOWCYsr5+Q+JAi_zA_gEHmOU1J3fvq8jnd@mail.gmail.com \
    --to=avarab@gmail.com \
    --cc=brian@gernhardtsoftware.com \
    --cc=charles@hashpling.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).