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

[PATCH 0/1] Proactively fix a test issue with v3.x of the MSYS2 runtime

From
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Date
May 7, 2019, 21:51 UTC
Message-ID
<pull.185.git.gitgitgadget@gmail.com>

I saw this in one of my builds that followed the bleeding edge of Git for Windows' SDK: git.exe has a different idea of the test script's PID than the test script itself. Yet another of the quirks Git for Windows has to deal with...

Johannes Schindelin (1):
  t6500(mingw): use the Windows PID of the shell
 t/t6500-gc.sh | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)
base-commit: 8104ec994ea3849a968b4667d072fedd1e688642
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-185%2Fdscho%2Ft6500-and-msys2-runtime-v3.x-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-185/dscho/t6500-and-msys2-runtime-v3.x-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/185
-- 
gitgitgadget
Next: Johannes Schindelin via GitGitGadget
Message 1 of 5 in “Proactively fix a test issue with v3.x of the MSYS2 runtime”
  1. 0/1 Proactively fix a test issue with v3.x of the MSYS2 runtimeJohannes Schindelin via GitGitGadget, May 7, 2019
  2. 1/1 t6500(mingw): use the Windows PID of the shellJohannes Schindelin via GitGitGadget, May 7, 2019
  3. Eric SunshineMay 7, 2019
  4. Junio C HamanoMay 8, 2019
  5. Junio C HamanoMay 8, 2019

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.