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 603C2B9F for ; Wed, 19 Apr 2017 20:27:54 +0000 (UTC) Received: from mx1.suse.de (mx2.suse.de [195.135.220.15]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D44D6202 for ; Wed, 19 Apr 2017 20:27:53 +0000 (UTC) Date: Wed, 19 Apr 2017 22:27:51 +0200 (CEST) From: Jiri Kosina To: James Bottomley In-Reply-To: <1492633237.3217.50.camel@HansenPartnership.com> Message-ID: References: <1492633237.3217.50.camel@HansenPartnership.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: ksummit , Dave Airlie , Greg Kroah-Hartman , David Miller , Doug Ledford , Ingo Molnar Subject: Re: [Ksummit-discuss] "Maintainer summit" invitation discussion List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 19 Apr 2017, James Bottomley wrote: > 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. Just to make sure that we don't repeat a discussion that has already happened, see my proposal from 2015 https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2015-July/001287.html It didn't receive too much positive traction though. -- Jiri Kosina SUSE Labs