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

Re: What's cooking in git.git (Jan 2022, #03; Thu, 13)

From
David Aguilar <davvid@gmail.com>
Date
Jan 15, 2022, 16:45 UTC
Message-ID
<CAJDDKr7bYP7JNmY7XML0rkxv8uCKAbO-LdAAn0KkyTq3UX4hkg@mail.gmail.com>
In-Reply-To
<xmqq35lrf8g4.fsf@gitster.g>
On Fri, Jan 14, 2022 at 7:16 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 13 quoted lines
>
> There are a few "oops, what we merged recently is broken" topics
> that still are not in 'master', but otherwise what we have should
> be pretty much what we'll have in the final one.
>
>  - I am reasonably happy with ab/refs-errno-cleanup (just one patch)
>    that fixes the incorrect state of the code left by the earlier
>    parts of the topic that have already been merged during this
>    cycle.
>
>  - I am also OK with ab/reftable-build-fixes (two patches), one for
>    general type correctness fix, the other for helping older sub-C99
>    compilers.

I ran into the c99 test balloon. I get the (expected?) c99 build errors and an uncompress2 build error with RHEL7.9's stock gcc 4.8.5.

Are we dropping support for RHEL7.9?

Using NO_UNCOMPRESS2=YesPlease and CFLAGS += -std=c99 in config.mak works but I'm not sure if we actually expect users to deal with those details themselves.

Sorry for being out of the loop on the plan for older toolchains, but I wasn't sure if we should be expecting a patch that configures the default flags so that things build out of the box again or if this is considered the new status quo and we're okay regressing?

$ rpm -q zlib-devel zlib-devel-1.2.7-19.el7_9.x86_64

$ gcc -v ... gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC)

Was part of the intention of the test balloon to get reports of this nature? I checked the commit logs and related discussion but that didn't really clarify things.

It seems like that was the intention based on the note of, "any warnings will eventually surface." in the commit message for 5f46385309 (config.mak.dev: specify -std=gnu99 for gcc/clang, 2021-12-08).

I'll keep an eye out for any patches that I should test in this area.

cheers, -- David

Previous: Taylor BlauNext: Junio C Hamano
Message 17 of 19 in “What's cooking in git.git (Jan 2022, #03; Thu, 13)”
  1. Junio C HamanoJan 14, 2022
  2. Junio C HamanoJan 14, 2022
  3. Elijah NewrenJan 14, 2022
  4. Junio C HamanoJan 14, 2022
  5. Elijah NewrenJan 14, 2022
  6. Junio C HamanoJan 14, 2022
  7. Junio C HamanoJan 14, 2022
  8. Ævar Arnfjörð BjarmasonJan 14, 2022
  9. Patrick SteinhardtJan 17, 2022
  10. Mistakes in the stalled category? (Was: Re: What's cooking in git.git (Jan 2022, #03; Thu, 13))Elijah Newren, Jan 14, 2022
  11. Junio C HamanoJan 14, 2022
  12. Junio C HamanoJan 14, 2022
  13. Junio C HamanoJan 15, 2022
  14. Derrick StoleeJan 18, 2022
  15. en/present-despite-skipped & en/remerge-diff (Was: Re: What's cooking in git.git (Jan 2022, #03; Thu, 13))Elijah Newren, Jan 14, 2022
  16. tb/midx-bitmap-corruption-fix (was: Re: What's cooking in git.git (Jan 2022, #03; Thu, 13))Taylor Blau, Jan 14, 2022
  17. David AguilarJan 15, 2022
  18. Junio C HamanoJan 15, 2022
  19. David AguilarJan 16, 2022

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.