Re: v2.35.0 DEVELOPER=1 regression

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 15, 2022, 01:08 UTC
Message-ID: <xmqqfspp6c22.fsf@gitster.g>
In-Reply-To: <220115.86h7a5rfdu.gmgdl@evledraar.gmail.com>

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

> I'm just suggesting that perhaps a more practical solution is to
> side-step those portability issues by checking this in CI, which I think
> would be Good Enough on this case.

Use of GitHub PR + GGG is required to take advantage of that, no? I do not think I want to see a change that makes it _more_ likely that a patch I pick up from the list will have problems that my local integration work will not catch (because DEVELOPER=YesPlease build is castrated at the original contributor side, and also on my box) and will only be caught after I push out 'seen'.

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