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

Re: "./t0001-init.sh --valgrind" is broken

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 3, 2016, 02:57 UTC
Message-ID
<xmqqsi082rqc.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CACsJy8AL_RGEb2z44-yoL+3yF7n1+FMLqZkmWwUDFJnEPYS_nw@mail.gmail.com>
Duy Nguyen <pclouds@gmail.com> writes:
Show 9 quoted lines
> On Thu, Mar 3, 2016 at 7:07 AM, Christian Couder
> <christian.couder@gmail.com> wrote:
>> Hi,
>>
>> It looks like commit 57ea7123c86771f47f34e7d92d1822d8b429897a (git.c:
>> make sure we do not leak GIT_* to alias scripts, Dec 20 14:50:19 2015)
>> broke "./t0001-init.sh --valgrind".
>
> Just wanted to confirm the problem. I will look at it later today.
Thanks.
Previous: Duy NguyenNext: Johannes Sixt
Message 3 of 9 in “"./t0001-init.sh --valgrind" is broken”
  1. Christian CouderMar 3, 2016
  2. Duy NguyenMar 3, 2016
  3. Junio C HamanoMar 3, 2016
  4. Johannes SixtMar 3, 2016
  5. Duy NguyenMar 3, 2016
  6. Duy NguyenMar 3, 2016
  7. Junio C HamanoMar 3, 2016
  8. Jeff KingMar 3, 2016
  9. Johannes SixtMar 3, 2016

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.