From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
"Bityutskiy, Artem" <artem.bityutskiy@intel.com>
Subject: Re: [git pull] drm for v4.7
Date: Wed, 25 May 2016 09:13:35 -0700 [thread overview]
Message-ID: <CA+55aFwx6cY45QWVaO2HpSAvbz-bMqC2sFz3+NnKSC4B8xECkg@mail.gmail.com> (raw)
In-Reply-To: <8737p6czij.fsf@intel.com>
On Wed, May 25, 2016 at 1:28 AM, Jani Nikula
<jani.nikula@linux.intel.com> 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
next prev parent reply other threads:[~2016-05-25 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 6:41 Dave Airlie
2016-05-23 18:59 ` Linus Torvalds
2016-05-23 19:10 ` Linus Torvalds
2016-05-25 2:03 ` Stephen Rothwell
2016-05-25 8:28 ` Jani Nikula
2016-05-25 16:13 ` Linus Torvalds [this message]
2016-05-25 16:49 ` Emil Velikov
2016-05-23 19:20 ` Dave Airlie
2016-05-23 19:23 ` Dave Airlie
2016-05-23 19:55 ` Dave Airlie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+55aFwx6cY45QWVaO2HpSAvbz-bMqC2sFz3+NnKSC4B8xECkg@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=artem.bityutskiy@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®