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

Re: [PATCH v2] t3310: avoid hiding failures from rev-parse in command substitutions

From
Francesco Paparatto <francescopaparatto@gmail.com>
Date
Mar 5, 2026, 22:42 UTC
Message-ID
<CAEaT9_-h2MEshMHoyoW9kWQgt_EfQJXcxWSn+cXTSL4mKME=5w@mail.gmail.com>
In-Reply-To
<xmqq5x7a3x9w.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
> Hmph, did I suggest this?  I know Eric had comments on a previous
> round, and the improvements in this patch seems to be influenced a
> lot stronger by his input than whatever I may have said.

Sorry about the Suggested-by line. I added it because of your earlier comment here:

    https://public-inbox.org/git/xmqqv7fioueg.fsf@gitster.g/

but you're right that the concrete changes in this version were mostly influenced by Eric's review, so I'll drop that trailer.

> On top of what commit is this patch designed to apply?
This patch is based on top of:
    b3ec5aec2367262f464a33d6eab7a9f49fd413f1
    ("t3310: replace test -f/-d with test_path_is_file/test_path_is_dir")
I'll reroll and send a v3 of the patch shortly.

Thanks, Francesco

Previous: Junio C HamanoNext: Francesco Paparatto
Message 9 of 15 in “t3310: avoid hiding failures from rev-parse in command substitutions”
  1. t3310: avoid hiding failures from rev-parse in command substitutionsFrancesco Paparatto, Mar 4, 2026
  2. Eric SunshineMar 4, 2026
  3. t3310: avoid hiding failures from rev-parse in command substitutionsFrancesco Paparatto, Mar 5, 2026
  4. Junio C HamanoMar 5, 2026
  5. Eric SunshineMar 5, 2026
  6. Francesco PaparattoMar 5, 2026
  7. Junio C HamanoMar 5, 2026
  8. Junio C HamanoMar 5, 2026
  9. Francesco PaparattoMar 5, 2026
  10. t3310: avoid hiding failures from rev-parse in command substitutionsFrancesco Paparatto, Mar 5, 2026
  11. Eric SunshineMar 7, 2026
  12. Francesco PaparattoMar 7, 2026
  13. t3310: avoid hiding failures from rev-parse in command substitutionsFrancesco Paparatto, Mar 7, 2026
  14. Eric SunshineMar 8, 2026
  15. Junio C HamanoMar 8, 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.