# Subject: [PATCH 0/2] misc Makefile patches 2 messages from 2024-07-18 to 2024-07-18. Participants: Ramsay Jones, Junio C Hamano. Thread: https://gitlist.dev/t/61800 ## Ramsay Jones, 2024-07-18 01:10 Subject: Subject: [PATCH 0/2] misc Makefile patches Message-ID: <7a38d869-8d8a-4922-894c-59ac7fc20449@ramsayjones.plus.com> URL: https://gitlist.dev/e/7a38d869-8d8a-4922-894c-59ac7fc20449%40ramsayjones.plus.com ``` These patches have been hanging around for _years_, so I rebased them onto the current master branch @ 04f5a52757 ("Post 2.46-rc0 batch #2", 2024-07-16). This was prompted by the sparse discussion tonight. Ramsay Jones (2): Makefile: drop -Wno-universal-initializer from SP_EXTRA_FLAGS config.mak.uname: remove unused uname_P variable Makefile | 2 +- config.mak.uname | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) -- 2.45.0 ``` ## Junio C Hamano, 2024-07-18 04:50 Subject: Re: Subject: [PATCH 0/2] misc Makefile patches Message-ID: URL: https://gitlist.dev/e/xmqqle1z1ey9.fsf%40gitster.g In-Reply-To: <7a38d869-8d8a-4922-894c-59ac7fc20449@ramsayjones.plus.com> ``` Ramsay Jones writes: > These patches have been hanging around for _years_, so I rebased them > onto the current master branch @ 04f5a52757 ("Post 2.46-rc0 batch #2", > 2024-07-16). This was prompted by the sparse discussion tonight. I do not see any immediate downside, but lack of immediate upside matters a lot more at this phase in the cycle. I may queue them but neither looks worth disrupting the upcoming release. So it would have to wait before the 2.46 final before it hits the 'master' track. Thanks. ```