Re: [Ksummit-discuss] [CORE TOPIC] Recruitment (Reviewers, Testers, Maintainers, Hobbyists)

[Darren Hart <dvhart@infradead.org>]

On Sun, Jul 12, 2015 at 11:27:08PM +0200, Peter Hüwe wrote:
> Am Samstag, 11. Juli 2015, 17:04:37 schrieb Greg KH:
> > On Fri, Jul 10, 2015 at 07:39:46PM -0700, Darren Hart wrote:
> > > OK, all good points. It looks as though I can step up my own tooling some
> > > to make the email-to-compilation step faster so I don't spend as much
> > > time on patches with compiler warnings, that don't apply, etc. Dan C.
> > > said something similar.
> > 
> > I think I mentioned it before, but Wolfram has a set of scripts that
> > does this really well.  I don't know if they are published anywhere, but
> > that would be a good place to start with.  I think Sara Sharp also had a
> > bunch that she used to make life easier, you might want to ask her the
> > next time you see her in the office.
> 
> 
> They are called ninja-check and published here
> https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2014-May/000554.html
> 
> Ksummit Thread about all these tools can be found here:
> ftp://kernel.mirrors.pair.com/pub/linux/kernel/people/paulmck/LKS/LKS2014Topic/000291.html

Thank you all very much for these pointers. I have ninja-check up and running
all the checkers now. Between these and:

http://www.do-not-panic.com/2014/07/applying-patches-from-mutt-onto-git.html
(view source for actual .muttrc as his blog hides <pipe-entry> and <tag-prefix>)

And Ben's original:
http://flavioleitner.blogspot.com/2011/03/patch-workflow-with-mutt-and-git.html

I added a checkpatch binding as well.

I now have a much more capable mutt-to-git interface which should help a ton. It
took me a day while dodging everything else I could, and I'll continue to tweak
it forever of course. Well worth the effort.

-- 
Darren Hart
Intel Open Source Technology Center