Re: [PATCH] t4013: add expected failure for "log --patch --no-patch"

From: Junio C Hamano <gitster@pobox.com>
Date: May 3, 2023, 18:07 UTC
Message-ID: <xmqqmt2lqofb.fsf@gitster.g>
In-Reply-To: <874jote2zl.fsf@osv.gnss.ru>

Sergey Organov <sorganov@gmail.com> writes:

> No problem from my side, but are you sure?

Absolutely.

I've seen people just say "we document a failed one" and leave it at that, without attempting to fix. I am trying to see if pushing back at first would serve as a good way to encourage these known failure to be fixed, without accumulating too many expect_failure in our test suite, which will waste cycles at CI runs (which do not need to be reminded something is known to be broken). I will try not to do this when I do not positively know the author of such a patch is capable enough to provide a fix, though, and you are unlucky enough to have shown your abilities in the past ;-)

Thanks.

$ 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.