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 F003CABA for ; Wed, 8 Jul 2015 07:35:53 +0000 (UTC) Received: from mail.emea.novell.com (mail.emea.novell.com [130.57.118.101]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6CFD412D for ; Wed, 8 Jul 2015 07:35:53 +0000 (UTC) Date: Wed, 8 Jul 2015 09:35:38 +0200 (CEST) From: Jiri Kosina To: Mark Brown In-Reply-To: <20150707224025.GJ11162@sirena.org.uk> Message-ID: References: <20150707224025.GJ11162@sirena.org.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [CORE TOPIC] services needed from kernel.org infrastructure List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 7 Jul 2015, Mark Brown wrote: > > I personally would very welcome a facility that'd send out an e-mail if a > > new commit is pushed to a git.kernel.org repo branch (sort of what tip-bot > > and akpm's scripts are doing these days) to automatically notify the patch > > author that the patch has been merged and pushed out. > > Those are useful, I know Greg has one and I just wrote one too. I'm not > sure it needs to be on the server side though, they can also be done > from the client which lets you try to fine tune things more readily. I explicitly proposed these to be (to some extent configurable) server-side hooks, exactly to avoid every committer maintaining his own set of home-brew scripts. -- Jiri Kosina SUSE Labs