git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] t7510: do not fail when gpg warns about insecure memory

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Mar 8, 2015, 22:04 UTC
Message-ID
<20150308220424.GD4245@vauxhall.crustytoothpaste.net>
In-Reply-To
<CAPig+cQXJgZJAoyQVYg3CNNzd70eA=ttdL7=g6wabtBkWBijeQ@mail.gmail.com>
On Sun, Mar 08, 2015 at 05:43:41PM -0400, Eric Sunshine wrote:
Show 13 quoted lines
>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.
Perhaps this is better?
  Unfortunately when running the test, that message is found in the 
  standard output of git show -s --show-signature, but in the standard 
  error of git verify-commit -v causing the comparisons of both standard 
  output and standard error to fail.
-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Previous: Eric SunshineNext: Eric Sunshine
Message 3 of 9 in “t7510: do not fail when gpg warns about insecure memory”
  1. t7510: do not fail when gpg warns about insecure memoryKyle J. McKay, Mar 8, 2015
  2. Eric SunshineMar 8, 2015
  3. brian m. carlsonMar 8, 2015
  4. Eric SunshineMar 8, 2015
  5. brian m. carlsonMar 9, 2015
  6. Kyle J. McKayMar 9, 2015
  7. Michael J GruberMar 9, 2015
  8. t7510: do not fail when gpg warns about insecure memoryKyle J. McKay, Mar 9, 2015
  9. Michael J GruberMar 10, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.