From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 3E4A9BC8 for ; Fri, 10 Jul 2015 20:56:10 +0000 (UTC) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9A415179 for ; Fri, 10 Jul 2015 20:56:09 +0000 (UTC) Date: Fri, 10 Jul 2015 13:56:06 -0700 From: josh@joshtriplett.org To: David Woodhouse Message-ID: <20150710205606.GC10533@cloud> References: <201507080121.41463.PeterHuewe@gmx.de> <559C73DF.2030008@roeck-us.net> <20150708114011.3a1f1861@noble> <2879113.fraeuJIr2M@avalon> <20150709193718.GD9169@vmdeb7> <1436481109.3324.219.camel@infradead.org> <20150710003559.GT11162@sirena.org.uk> <20150710020706.GH111846@vmdeb7> <20150710155144.34dde697@gandalf.local.home> <1436558412.24408.35.camel@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1436558412.24408.35.camel@infradead.org> Cc: ksummit-discuss@lists.linuxfoundation.org, Jason Cooper Subject: Re: [Ksummit-discuss] [CORE TOPIC] Recruitment (Reviewers, Testers, Maintainers, Hobbyists) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, Jul 10, 2015 at 09:00:12PM +0100, 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? Nope, I do that too. (Though then I have to resist the temptation to just fix it in the mailer rather than fixing the original and regenerating.) > 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? git-imap-send does exactly that. The one issue I've observed with git-imap-send: many mailers, including mutt, will ignore the generated Message-Id, In-Reply-To, and References headers in the drafts, and generate new ones that break threading. That's why I stopped using it and started using mutt -H. - Josh Triplett