Ihor Dutchak

> Why is that desirable? To preserve git history - it matters:  If we apply `.clang-format` to all existing code - _a lot_ of immediate blame/history will be hidden...

Interesting, this [option](https://docs.github.com/en/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view) is only [recently](https://github.com/orgs/community/discussions/5033#discussioncomment-2318478) supported by Github itself. That is actually a gamechanger (at least to me).

Optione 3 is something that hasn't been on the table and looks interesting. Does git preserves a file history when it is moved to a different folder?

> Subversion does, so surely git I wouldn't be so sure - need to check.

This will break the ABI backward compatibility. It gets even worse, when the library is built with C23, installed into a system/etc., and then some other application is built with...

> And for private enums, we can change the ABI/API, can we not? Yes, that shold not harm. > Only if the size/sign/type is actually changed (as opposed to merely...

@tormodvolden do you happen to have an oppinion on this one?

> But for me, opting into a new language version (with -std=c23), is a good opportunity for a small compatibility break. That's a _huge_ compatibility break :) To have it...

Can you make another draft/PR with formatting already applied? (and include `.git-blame-ignore-revs`, if feasible)

> more feedback from others about what options the project wants Because most of us are not clang-format options experts, it is hard to tell w/o applying and checking what's...