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

[Tim Bird <tim.bird@sonymobile.com>]

On 07/10/2015 12:51 PM, Steven Rostedt wrote:
> On Thu, 9 Jul 2015 19:07:06 -0700
> Darren Hart <dvhart@infradead.org> wrote:
> 
>  
>> As far as recruitment goes, I think we're talking about barriers to first-timers
>> and such - and git-send-email is one of those things. Eventually, a developer
> 
> +1000
> 
> I still don't use git-send-email, as I afraid that I'll blow it and end
> up sending a thousand patches to every developer that ever touched the
> kernel ;-)

I'm in exactly the same boat.  I don't submit patches frequently enough
that I trust a git-send-email workflow.  It's too automated for me.
I'd rather take the extra time to manually format my patch e-mails and my
CC: lists, than be embarrassed.  Of course then I make manual mistakes
and end up getting embarrassed sometimes anyway, but I can usually
avoid a patch embarrassment armageddon.

But my manual steps and self-verification are a lot of work each time, so
some automation would be very much appreciated.
 
> I still use quilt to send my patch series. Just because I know how it
> works and I trust it. And I get to see exactly what it is about to send
> (the only thing it can send is what's in the patches/ directory,
> nothing else).
> 
> I have a script that takes my git tree and creates the patches in a
> format that quilt will send them nicely.

Maybe it would be good for a patch submission tool be able to single-step
through the submission preparation, both so that developers can learn
from it and not just use it as a crutch, and also to allow
developers to intervene if it's about to do something stupid.
 -- Tim