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

Re: [PATCH] wrapper: remove xunsetenv()

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 29, 2021, 21:53 UTC
Message-ID
<xmqqo877ijl1.fsf@gitster.g>
In-Reply-To
<20211029212705.31721-1-carenas@gmail.com>
Carlo Marcelo Arenas Belón  <carenas@gmail.com> writes:
> Platforms that are using the git compatibility layer for unsetenv
> use void as a return value for unsetenv(), so any function that checks
> for a return value will fail to build.

It sounds like barking up a wrong tree. unsetenv() is supposed to signal success with 0 and failure with -1, and the compat/ implementation is broken, not the caller that tries to be nice and check the error return from the system function it calls.

Not that adding the unused wrapper, and leaving it unused, was a wise decision in hindsight, though.

Previous: rsbecker@nexbridge.com
Message 17 of 17 in “wrapper: remove xunsetenv()”
  1. wrapper: remove xunsetenv()Carlo Marcelo Arenas Belón, Oct 29, 2021
  2. Jeff KingOct 29, 2021
  3. rsbecker@nexbridge.comOct 29, 2021
  4. Carlo ArenasOct 29, 2021
  5. Junio C HamanoOct 29, 2021
  6. Jeff KingOct 29, 2021
  7. Junio C HamanoOct 29, 2021
  8. Jeff KingOct 29, 2021
  9. Junio C HamanoOct 29, 2021
  10. Jeff KingOct 29, 2021
  11. rsbecker@nexbridge.comOct 29, 2021
  12. Junio C HamanoOct 29, 2021
  13. rsbecker@nexbridge.comOct 30, 2021
  14. rsbecker@nexbridge.comOct 29, 2021
  15. Carlo ArenasOct 29, 2021
  16. rsbecker@nexbridge.comOct 29, 2021
  17. Junio C HamanoOct 29, 2021

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.