> On 9/11/15 5:16 AM, Malahal Naineni wrote:
> > pycheckpatch is only run when you explicitly run it. checkpatch.pl is
> > run as part of a githook, so this must be it!
> >
> > What git command were you running to get this? In any case, looks like
> > you don't have ganesha checkpath config file in the correct place, so
> > the script was using default config which assumes it is a linux kernel!
> >
> Many of them.  git commit --amend -a comes to mind.
> 
> 
> > Did you happen to remove .checkpatch.conf from your repo?
> >
> Not that I'm aware of, it had been running just fine before I'd tried sucking
> down Dan's gerrithub stuff.
> 
> Anyway, what's working for me now -- after making a new repo, do *NOT*
> run scripts/git-hooks/install-git-hooks.sh
> 
> So I have no hooks at all at the moment, and git life is better.
> 
> In the future, I'll just let gerrithub handle it instead.

Please install the checkpatch githook. It really makes my life easier when MOST 
patches come in passing checkpatch.

Thanks

Frank


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


------------------------------------------------------------------------------
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Reply via email to