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

[Laurent Pinchart]

On Friday 10 July 2015 21:00:12 David Woodhouse wrote:
> On Fri, 2015-07-10 at 15:51 -0400, Steven Rostedt wrote:
> > On Thu, 9 Jul 2015 19:07:06 -0700 Darren Hart 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 ;-)
> 
> Rather than sending messages, it's actually better to put them as
> *drafts*, ready to be sent by the user's normal mailer. It's not hard
> to do this — I usually dump the mails into
> ~/.local/share/evolution/mail/local/.Drafts/new/ for example.
> 
> And then I can *read* them before sending them, which is good practice
> anyway. Am I the only person who often finds a final minor nit with
> their own patch, in that final read-through just before hitting 'send'
> on an email?

Certainly not, but what prevents you from doing that with git-send-email ? In 
my workflow I always format patches with git-format-patch, proof-read them 
with my favourite $EDITOR and then use git-send-email to send them.

> Perhaps we should provide tools which make it trivial to do the same
> for various different mail clients, without users having to know where,
> and in what form, their drafts folders are?

-- 
Regards,

Laurent Pinchart