From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755801AbcEYQNo (ORCPT ); Wed, 25 May 2016 12:13:44 -0400 Received: from mail-io0-f182.google.com ([209.85.223.182]:36277 "EHLO mail-io0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755770AbcEYQNm (ORCPT ); Wed, 25 May 2016 12:13:42 -0400 MIME-Version: 1.0 In-Reply-To: <8737p6czij.fsf@intel.com> References: <20160525120318.407c3aa0@canb.auug.org.au> <8737p6czij.fsf@intel.com> Date: Wed, 25 May 2016 09:13:35 -0700 X-Google-Sender-Auth: 2bGNf1_NVfuyJztJ8-yXT5M7MBg Message-ID: Subject: Re: [git pull] drm for v4.7 From: Linus Torvalds To: Jani Nikula Cc: Stephen Rothwell , Linux Kernel Mailing List , DRI mailing list , "Bityutskiy, Artem" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 25, 2016 at 1:28 AM, Jani Nikula wrote: > > There may be better ones out there, but Artem's "aiaiai" has some > helpers [1] for diffing build logs, if you want something simple to > integrate into existing scripts. It would be lovely to have some kind of warning detection, but quite frankly, just doing a build and counting lines in 'stderr' from the build and having some trigger for "oops, lots of new lines" would be sufficient. So I don't think anything really fancy to diff build logs is necessarily needed, although the people who then get the report about "your merge causes lots of new warnings" might appreciate it. Linus