Automatic code formatting about nfs-ganesha HOT 4 OPEN

This will require a re-submit when we are ready to merge it. We're not quite ready, but soon...

from nfs-ganesha.

Push a patch to gerrithub and let's talk.

from nfs-ganesha.

I uploaded the commits for that for review- https://review.gerrithub.io/q/topic:clang-format

Note that for the commit- https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1187343, checkpatch has many warnings and errors
Most are false positive and I saw discussions for (for example not recognizing a pointer correctly and mistaking it to be a multiplication operator that requires spaces around it).

I added a commit that changes the pre-commit hooks to verify the clang-format.
Clang-format has integration with many IDEs so developers can configure their IDE to use clang-format to automatically format their code without dealing with formatting at all.

We can also add to gerrit a clang-format verifier instead of the existing checkpath.

If that will be accepted I'll also update the documentation regarding clang-format instead of checkpatch.pl.

from nfs-ganesha.

I uploaded the commits for that for review- https://review.gerrithub.io/q/topic:clang-format

Note that for the commit- https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/1187343, checkpatch has many warnings and errors Most are false positive and I saw discussions for (for example not recognizing a pointer correctly and mistaking it to be a multiplication operator that requires spaces around it).

I added a commit that changes the pre-commit hooks to verify the clang-format. Clang-format has integration with many IDEs so developers can configure their IDE to use clang-format to automatically format their code without dealing with formatting at all.

We can also add to gerrit a clang-format verifier instead of the existing checkpath.

If that will be accepted I'll also update the documentation regarding clang-format instead of checkpatch.pl.

please resolve the conflict files on gerrit.

from nfs-ganesha.