Documentation | eng/vc-users: update guidance on commit messages (!214)

[Gedare Bloom (@gedare)]

Gedare Bloom commented on a discussion on eng/vc-users.md: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/214#note_140573

 > +- 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'd rather not, instead we should point to the documentation to help users who run into CI warnings/errors.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/214#note_140573
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260131/9ff15c92/attachment-0001.htm>