This is only tangentially on topic, but I have a git pre-commit hook
which detects .orig files and trailing whitespace.  It's saved me a
lot of embarrassment.

I also have a git tool which will fix trailing whitespace in your patch.

https://github.com/jlebar/moz-git-tools#pre-commit
https://github.com/jlebar/moz-git-tools#git-fix-whitespace

On Mon, May 27, 2013 at 10:54 PM, Anthony Jones <ajo...@mozilla.com> wrote:
> On 25/05/13 04:16, Ehsan Akhgari wrote:
>> On 2013-05-24 11:46 AM, Benoit Girard wrote:
>> Another option is to use clang-format, which can lexically parse diff
>> files.
>
> A pre-upload check would give the fastest feedback.
>
> It would help me (and those who review my code) if there is an easy way
> to check my patches from the command line before doing hg bzexport. Even
> if it is only for white space. What we need is a way to specify which
> file paths the standard formatting rules apply to. I just need to figure
> out how to install clang-format.
>
> If this proves to be successful then we could consider putting effort
> into other style conventions.
>
> Anthony
>
> _______________________________________________
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to