From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthieu Moy Subject: Re: 0 bot for Git Date: Wed, 13 Apr 2016 14:30:06 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Cc: Junio C Hamano , Stefan Beller , lkp@intel.com, Greg KH , "git\@vger.kernel.org" To: Lars Schneider X-From: git-owner@vger.kernel.org Wed Apr 13 14:30:59 2016 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aqJwg-0002lt-AV for gcvg-git-2@plane.gmane.org; Wed, 13 Apr 2016 14:30:58 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759278AbcDMMah (ORCPT ); Wed, 13 Apr 2016 08:30:37 -0400 Received: from mx1.imag.fr ([129.88.30.5]:51342 "EHLO mx1.imag.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759195AbcDMMag (ORCPT ); Wed, 13 Apr 2016 08:30:36 -0400 Received: from clopinette.imag.fr (clopinette.imag.fr [129.88.34.215]) by mx1.imag.fr (8.13.8/8.13.8) with ESMTP id u3DCU5hm015444 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 13 Apr 2016 14:30:05 +0200 Received: from anie (anie.imag.fr [129.88.7.32]) by clopinette.imag.fr (8.13.8/8.13.8) with ESMTP id u3DCU6eC011744; Wed, 13 Apr 2016 14:30:06 +0200 In-Reply-To: (Lars Schneider's message of "Wed, 13 Apr 2016 14:16:54 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (mx1.imag.fr [129.88.30.5]); Wed, 13 Apr 2016 14:30:06 +0200 (CEST) X-IMAG-MailScanner-Information: Please contact MI2S MIM for more information X-MailScanner-ID: u3DCU5hm015444 X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-SpamCheck: X-IMAG-MailScanner-From: matthieu.moy@grenoble-inp.fr MailScanner-NULL-Check: 1461155406.31787@VvCnQPoTtjT7Zmw7k7Y5Yw Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Lars Schneider writes: >> On 13 Apr 2016, at 07:43, Matthieu Moy wrote: >> >> Junio C Hamano writes: >> >>> Matthieu Moy writes: >>> >>> True, presumably the Travis integration already solves that part, so >>> I suspect it is just the matter of setting up: >>> >>> - a fork of git.git and have Travis monitor any and all new >>> branches; >>> >>> - a bot that scans the list traffic, applies each series it sees to >>> a branch dedicated for that series and pushes to the above fork. >> >> ... and to make it really useful: a way to get a notification email sent >> on-list or at least to the submitter as a reply to the patch series. >> Just having a web interface somewhere that knows how broken the code is >> would not be that useful. > > Travis CI could do this but I intentionally disabled it to not annoy anyone. > It would be easy to enable it here: > https://github.com/git/git/blob/7b0d47b3b6b5b64e02a5aa06b0452cadcdb18355/.travis.yml#L98-L99 The missing part would be "as a reply to the patch series". When I start reviewing a series, if the patch is broken and the CI system already knows, I'd rather have the information attached in the same thread right inside my mailer. -- Matthieu Moy http://www-verimag.imag.fr/~moy/