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

Re: [PATCH] lazyload: use correct calling conventions

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 11, 2022, 13:17 UTC
Message-ID
<nycvar.QRO.7.76.6.2201111412300.1081@tvgsbejvaqbjf.bet>
In-Reply-To
<xmqqh7abxmxs.fsf@gitster.g>
Hi Junio,
On Mon, 10 Jan 2022, Junio C Hamano wrote:
Show 5 quoted lines
> Dscho, how does this look?  My choices are
>
>  - Waiting for review.
>  - Will merge to 'next'.
>  - Will merge to 'next' and then to 'master'.
My preference is the last option, merge it down quickly.
> The last one will make it as part of Git 2.35.0 final, unless there
> is some unexpected breakage found later.

I do not expect anything to break. Just like Matthias, I actually expect future breakages to be fended off by this.

Merging it into v2.35.0 final will require a tiny fixup in `compat/win32/flush.c` (which we carry in Git for Windows already), but that's a much smaller deal than the fall-out of the v2.34.0 refactorings we had to deal with.

Thank you, Dscho

Previous: Junio C HamanoNext: Johannes Schindelin
Message 3 of 5 in “lazyload: use correct calling conventions”
  1. lazyload: use correct calling conventionsMatthias Aßhauer via GitGitGadget, Jan 8, 2022
  2. Junio C HamanoJan 10, 2022
  3. Johannes SchindelinJan 11, 2022
  4. Johannes SchindelinJan 11, 2022
  5. Junio C HamanoJan 12, 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.