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

[Guenter]

On Fri, Jul 10, 2015 at 01:03:16PM -0700, Tim Bird wrote:
> On 07/10/2015 12:51 PM, Steven Rostedt wrote:
> > On Thu, 9 Jul 2015 19:07:06 -0700
> > Darren Hart <dvhart at 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.
> 
I use git send-email, but I don't use it blindly. If I use it directly,
I give it a trial first with --dry-run. For patch series I use a directory
to collect the patches and then use a script to actually send them.
Sometimes I also use --cc-cmd with a script I have written to automatically
add Cc's, but never without dry-run.

Guenter