mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <>
To: Vasco Almeida <>
Cc:, Heiko Voigt <>,
	Stefan Beller <>
Subject: Re: [PATCH 1/3] t3404: become resilient to GETTEXT_POISON
Date: Wed, 17 Aug 2016 14:49:30 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1608171448060.4924@virtualbox> (raw)
In-Reply-To: <>

Hi Vasco,

On Fri, 12 Aug 2016, Vasco Almeida wrote:

> The concerned test greps the output of exit_with_patch() in
> script.
> Signed-off-by: Vasco Almeida <>

Thank you for keeping an eye out for these issues. I have to admit that I
am a bit confused when to use i18ngrep and when not, so it is good to know
that my mistakes won't survive for long!


      parent reply	other threads:[~2016-08-17 12:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-12 11:59 [PATCH 1/3] t3404: become resilient to GETTEXT_POISON Vasco Almeida
2016-08-12 11:59 ` [PATCH 2/3] t5520: " Vasco Almeida
2016-08-12 11:59 ` [PATCH 3/3] t7411: " Vasco Almeida
2016-08-17 12:49 ` Johannes Schindelin [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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1608171448060.4924@virtualbox \ \ \ \ \ \

* 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

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).