I was looking over https://wiki.openafs.org/devel/CodingStyle/ and
wondered if it might be worth considering basing the OpenAFS style on
one of these:
https://llvm.org/docs/CodingStandards.html
https://google.github.io/styleguide/cppguide.html
https://www.chromium.org/developers/coding-style
https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style
clang-format lets you make a custom based off of these. In theory this
could allow regular runs of clang-format to fix style errors (or maybe a
gerrit hook similar to buildbot?) without having quite so many warnings
on the development site.
The git settings from https://wiki.openafs.org/devel/GitDevelopers/ are
great, but a tool you can automate might lower the intimidation factor a
bit.
Pat
--
Pat Riehecky
Fermi National Accelerator Laboratory
www.fnal.gov
www.scientificlinux.org
_______________________________________________
OpenAFS-devel mailing list
OpenAFS-devel@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-devel
