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

Re: What's cooking in git.git (Aug 2020, #01; Mon, 3)

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 4, 2020, 18:58 UTC
Message-ID
<xmqqr1sms0f0.fsf@gitster.c.googlers.com>
In-Reply-To
<20200804185057.GA1400256@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 33 quoted lines
> On Mon, Aug 03, 2020 at 10:35:40PM -0700, Junio C Hamano wrote:
>
>> * ss/cmake-build (2020-06-26) 8 commits
>>   (merged to 'next' on 2020-08-03 at a0d70165c1)
>>  + ci: modification of main.yml to use cmake for vs-build job
>>  + cmake: support for building git on windows with msvc and clang.
>>  + cmake: support for building git on windows with mingw
>>  + cmake: support for testing git when building out of the source tree
>>  + cmake: support for testing git with ctest
>>  + cmake: installation support for git
>>  + cmake: generate the shell/perl/python scripts and templates, translations
>>  + Introduce CMake support for configuring Git
>> 
>>  Originally merged to 'next' on 2020-08-01
>> 
>>  CMake support to build with MSVC for Windows bypassing the Makefile.
>> 
>>  Will merge to 'master'.
>>  cf. https://github.com/git/git/runs/892824895
>
> I ran into issues with this, as I have several in-progress topics (not
> yet sent to the list) that touch our Makefile, and they needed updates
> to the cmake file (because it reproduces a lot of the lists and logic
> from the Makefile).
>
> The original philosophy behind putting it in contrib is that most people
> wouldn't have to care, and folks interested in cmake would be
> responsible for keeping it up to date. But the top patch makes it hard
> to ignore, because the vs-build CI job will fail.
>
> I'm not sure of the right path forward. I was definitely unenthused to
> be dealing with cmake, and the problem came up as soon as the series hit
> next.

My hope is that if we let vs-build broken long enough, those who want to see cmake to graduate would fix it. We can always threaten the topic to be discarded out of 'next' after the next release if it hasn't been fixed ;-)

Previous: Jeff KingNext: Jeff King
Message 3 of 15 in “What's cooking in git.git (Aug 2020, #01; Mon, 3)”
  1. Junio C HamanoAug 4, 2020
  2. Jeff KingAug 4, 2020
  3. Junio C HamanoAug 4, 2020
  4. Jeff KingAug 4, 2020
  5. Johannes SchindelinAug 12, 2020
  6. Jeff KingAug 12, 2020
  7. Sibi SiddharthanAug 12, 2020
  8. Jeff KingAug 12, 2020
  9. Junio C HamanoAug 12, 2020
  10. Jeff KingAug 12, 2020
  11. Johannes SchindelinAug 14, 2020
  12. Jeff KingAug 14, 2020
  13. Johannes SchindelinAug 17, 2020
  14. Junio C HamanoAug 17, 2020
  15. Jiang XinAug 6, 2020

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.