Amar Takhar commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5458#note_141302 We have other file formats to contend with not just C/C++, We have Python and MarkDown. None of the other tools "Just work" They will require running the local developer tools in order to run. Every single thing will require the developer tools to run. There is literally no advantage to this other than you want to be able to run clang-format on it's own and ignore all other types of formatting or spellcehcking and commit-message-checks. This is not a simple solution for contributors. A simple solution is to have it integrated into git and run on a 'git push' or install the tool and run it that automatically runs all of our checks. It will integrate fine into IDEs instead of running clang-format you run rtems-format for all source or rtems-check-commit to run all checks. If you want to run clang-format on its own you can use rtems-ci-stage get the config file(s) and run it yourself. I do not want anyone to be able to sidestep all the other checks in favour of source formatting. You won't convince me I've been down this road before there is no sidelining of the tools we already agreed to have put in place. I'm not interested in waiting until my tool is done because if it's this much of an argument to keep them out it will be an even harder argument to get them out. I was very up front about all of this, deciding to move ahead without letting me get my part done is a choice you've made and as I said, I'm fine with it. Keep your config files in a different branch on your repo and if anyone is interested in using it they can get the files from there for now. I can disable the C formatting for now until the rest is settled. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5458#note_141302 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
