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 1498EA67 for ; Fri, 21 Apr 2017 10:44:16 +0000 (UTC) Received: from ozlabs.org (ozlabs.org [103.22.144.67]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 38D1FE2 for ; Fri, 21 Apr 2017 10:44:15 +0000 (UTC) From: Michael Ellerman To: Mauro Carvalho Chehab , James Bottomley In-Reply-To: <20170420072413.11713d39@vento.lan> References: <1492633237.3217.50.camel@HansenPartnership.com> <20170420072413.11713d39@vento.lan> Date: Fri, 21 Apr 2017 20:34:10 +1000 Message-ID: <87y3uuaw2l.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain Cc: ksummit , Dave Airlie , Greg Kroah-Hartman , Ingo Molnar , Doug Ledford , David Miller Subject: Re: [Ksummit-discuss] "Maintainer summit" invitation discussion List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Mauro Carvalho Chehab writes: > Em Wed, 19 Apr 2017 13:20:37 -0700 > James Bottomley escreveu: > >> 1. Since most people agree that these form of notifications are useful, >> should we have a standard email for it (or at least a list of things >> which should be in that email, like commit-id, tree, maintainer, >> mailing list and the version of the kernel it is expected to be >> pushed for). >> 2. Given that we all run ad-hoc infrastructure to produce these emails, >> could we get a set of blessed scripts up on kernel.org for all >> comers so we can use the central infrastructure rather than rolling >> our own. > > I suspect that this very much depends on the way each maintainer handle > patches. For subsystems like media, where we use patchwork, notification > comes for free with the tool. AFAIK patchwork can only notify the submitter of the patch, which is OK, but I think it's preferable if the notification goes to the recipient list of the original mail. For example it's quite handy to know when another maintainer has merged a patch, so you don't merge it too, or wonder if you should. cheers