From: Eric Sunshine <sunshine@sunshineco.com>
Date: Sun, 08 Mar 2015 21:43:41 GMT
Subject: Re: [PATCH] t7510: do not fail when gpg warns about insecure memory
Message-ID: <CAPig+cQXJgZJAoyQVYg3CNNzd70eA=ttdL7=g6wabtBkWBijeQ@mail.gmail.com>
In-Reply-To: <2652cb72a82d4ca4be3ea90bafd263e@74d39fa044aa309eaea14b9f57fe79c>

On Sun, Mar 8, 2015 at 11:40 AM, Kyle J. McKay <mackyle@gmail.com> wrote:
> Depending on how gpg was built, it may issue the following
> message to stderr when run:
>
>   Warning: using insecure memory!
>
> Unfortunately when running the test, that message gets
> collected in the stdout result of git show -s --show-signature
> but is collected in the stderr result of git verify-commit -v

I'm having trouble parsing this. Is there a word missing?

> causing both the stdout and stderr result comparisions to fail.

s/comparisions/comparisons/

> Since checking for secure memory use by gpg is not the point of
> this test, filter out such messages to allow the test to pass
> even when gpg is "using insecure memory".
>
> Signed-off-by: Kyle J. McKay <mackyle@gmail.com>