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
Eric Sunshine <sunshine@sunshineco.com>
Date
Mar 8, 2015, 22:15 UTC
Message-ID
<CAPig+cTj_z0xpDmnSvb-S_wEbwzdcFsGwUkFdGWgcJhwZpfMFQ@mail.gmail.com>
In-Reply-To
<20150308220424.GD4245@vauxhall.crustytoothpaste.net>

On Sun, Mar 8, 2015 at 6:04 PM, brian m. carlson <sandals@crustytoothpaste.net> wrote:

Show 15 quoted lines
> On Sun, Mar 08, 2015 at 05:43:41PM -0400, Eric Sunshine wrote:
>> On Sun, Mar 8, 2015 at 11:40 AM, Kyle J. McKay <mackyle@gmail.com> wrote:
>>>   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?
> 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.

That doesn't help me parse it any better. It's the "but" without a corresponding "not" which seems to be throwing me off. Typically, one would write "this but not that" or "not this but that". I can't tell if there is a "not" missing or if the "but" is supposed to be an "and" or if something else was intended.

Previous: brian m. carlsonNext: brian m. carlson
Message 4 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.