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

Re: [PATCH 0/2] Organize mingw includes

From
Patrick Steinhardt <ps@pks.im>
Date
Oct 10, 2025, 09:53 UTC
Message-ID
<aOjXjEJePkpCDoI3@pks.im>
In-Reply-To
<pull.1985.git.1759995961.gitgitgadget@gmail.com>
On Thu, Oct 09, 2025 at 07:45:59AM +0000, Johannes Schindelin via GitGitGadget wrote:
> Following in the footsteps of the many, many recent #include refactorings,
> this patch series orders the #include statements in compat/mingw.c.

Both of these patches look good to me and I like the improved consistency that they bring. I may also do the same for our code in "refs/", where some of the files use relative includes, as well. Might be worth to document this somewhere if it isn't already, but that doesn't have to be part of your patch series here.

Sorting them also makes sense. It's another thing where I wish that we had a tool to enforce this. clang-format supports this in theory, but it's disabled right now. And I'm not even sure whether it can be told to include e.g. "git-compat-util.h" first.

Thanks!
Patrick
Previous: Johannes Schindelin via GitGitGadgetNext: Johannes Schindelin
Message 7 of 9 in “Organize mingw includes”
  1. 0/2 Organize mingw includesJohannes Schindelin via GitGitGadget, Oct 9, 2025
  2. 1/2 mingw: avoid relative `#include`sJohannes Schindelin via GitGitGadget, Oct 9, 2025
  3. Matthias AßhauerOct 11, 2025
  4. Johannes SixtOct 12, 2025
  5. Junio C HamanoOct 13, 2025
  6. 2/2 mingw: order `#include`s alphabeticallyJohannes Schindelin via GitGitGadget, Oct 9, 2025
  7. Patrick SteinhardtOct 10, 2025
  8. Johannes SchindelinOct 10, 2025
  9. Junio C HamanoOct 10, 2025

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.