Amar Takhar commented on a discussion on eng/vc-users.md: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/214#note_140567 > +- Please use a real name with a valid email address. Please do not use > + pseudonyms or provide anonymous contributions. > +- You can discuss the change spanning multiple commits in an Issue that > + can be referenced in the commit message. > +- For a patch series which impacts multiple BSPs, it is common to put each > BSP > + into a separate patch. This improves the quality and specificity of the > + commit messages. > +- If you change the formatting of source code in a repository please > + make that a separate patch and use "Formatting changes only" on the first > + line. Please indicate the reason or process. For example to "Conforming > + to code standing", "Reverting to upstream format", "Result of automatic > + formatting". > +- Similarly, if addressing a spelling, grammar, or Doxygen issue, please > + put that in a commit by itself separate from technical changes. > + > +### Commit Header I have updated the checker to enforce some new limitations on text before the `:` .. warning above 40 characters and failure above 45. See: * https://gitlab.rtems.org/administration/integration/-/commit/28f8cb01043e45503afd9fb3ef7e9e23ae965fc5 * https://gitlab.rtems.org/rtems/docs/rtems-docs/-/issues/132 -- View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/214#note_140567 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
