Amar Takhar commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5458#note_141496 The very idea that you think it's reasonable to: 1. Ignore commit message checks, python formatting, mardown formatting, spell check 2. Ask users to put `clang-format` manually into their IDE to get one type of check in earlier 3. Go back and say "Oh, now it's changed, you have to run these tools instead." On a purely procedural standpoint which I have been arguing the entire time this makes no sense. I do not want anyones first exposure to developer tools some side-line effort that circumvent the hard work I've put in on a full developer suite. You're free to disagree and that's your opinion. I want the first exposure to _any_ of this to be the full set of developer tools that encompass all developer tools and checks. You can very easily keep these config files on a branch in your own respository and anyone wanting to use them can get them from there, it's trivial to merge in the branch and remove it if anyone cares. Otherwise literally nothing else changes from what we have now. Writing this down now to discuss during the meeting tomorrow. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5458#note_141496 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
