Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
What I mean is in the global context of your planned work to fix the typos, which is very appreciated, but has to be coordinated and planned somehow, because the commit messages are not very explicit and repeat, then backports can be affected, making the release procedure more difficulat.
For example, the acc module got several PRs lately related to typos:
901d9cac2f 2023-02-04 15:28:48 +0200 Дилян Палаузов acc: typos
06ffb667b7 2022-12-24 16:38:35 +0200 Дилян Палаузов acc: typo fuNction
55c77f0966 2022-12-12 19:27:44 +0200 Дилян Палаузов acc: typos a/an
This PR has another commit to acc module. There are other types of typos, but then we need to understand how your work is planned and how can impact the development of the code. It is really nice to have good spelling, but if the writing/maintenance of the C code becomes to complex, we need to coordinate better.
Maybe we just keep this PR open until you consider all the spell checking work finished completely, then rebase and merge.
Of course, others can comment or suggest alternative to deal with it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.