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

[GSoC] Microproject: t4150 exit-code fix, is this instance still free?

From
GGEN-Z <duke2nuke4109@gmail.com>
Date
Nov 12, 2026, 19:31 UTC
Message-ID
<CAOaM9kds7LPvMgHkQoOwg0r9AmQyn41TptJKZ9ZECOJfc1mWzA@mail.gmail.com>
Hi,

I'm Aarambh Maan Shrestha, a 3rd-year B.Tech CSE (AI/ML) student at SRM Institute of Science and Technology, India. I use Git daily, and I've also re-implemented some of its plumbing (hashing, objects) in Python as a learning project, so I'd like to apply to Git for GSoC 2027.

For my microproject I picked "Avoid suppressing git's exit code in test scripts", the instance in t/t4150-am.sh, in the test 'am works with multi-line in-body headers', where 'git cat-file commit HEAD' is piped directly to grep (lines 1097-1098 on master). My plan is the usual fix from t8003: redirect the output to a temporary file first and use test_grep on it. I have the change ready locally and t4150 passes (87/87).

Before I send it: I searched the archive and found Trieu Huynh's 28 March 2026 series covering these same lines, which Junio asked to be dropped as a 16-patch series. The fix itself was never merged. Would a fresh single-file patch for just this t4150 instance still be welcome, or should I pick a different test script instead?

Thanks,
Aarambh Maan Shrestha
GitHub: Duke2nuke
Message 1 of 1 in “[GSoC] Microproject: t4150 exit-code fix, is this instance still free?”
  1. GEN-ZNov 12, 2026

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.