From: Kevin Wolf <kwolf@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Qemu-block <qemu-block@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 00/38] Block layer patches
Date: Tue, 6 Mar 2018 11:24:04 +0100 [thread overview]
Message-ID: <20180306102404.GB7139@localhost.localdomain> (raw)
In-Reply-To: <CAFEAcA_gi4Pt41arfrmseZzxs0YZtkvBShcszRftW0y0ar4Z1A@mail.gmail.com>
Am 06.03.2018 um 11:09 hat Peter Maydell geschrieben:
> On 5 March 2018 at 17:51, Kevin Wolf <kwolf@redhat.com> wrote:
> > The following changes since commit 86f4c7e05b1c44dbe1b329a51f311f10aef6ff34:
> >
> > Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20180302' into staging (2018-03-02 14:37:10 +0000)
> >
> > are available in the git repository at:
> >
> > git://repo.or.cz/qemu/kevin.git tags/for-upstream
> >
> > for you to fetch changes up to bfe1a14c180ec44c033be12b9151252ffda69292:
> >
> > block: Fix NULL dereference on empty drive error (2018-03-05 18:45:32 +0100)
> >
> > ----------------------------------------------------------------
> > Block layer patches
> >
> > ----------------------------------------------------------------
>
> This pull turns out to add a bunch of tests that end in the name "error",
> which triggers my buildlog scanning scripts that look for "error:".
> Could we rename those?
Wouldn't it make more sense to change your script so that it considers
"error" only if it's a whole word rather than part of an identifier?
These test cases concern error paths, so it's kind of expected that
their name contains "error" as a substring.
Kevin
next prev parent reply other threads:[~2018-03-06 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 17:51 [Qemu-devel] [PULL v2 00/38] Block layer patches Kevin Wolf
2018-03-06 10:09 ` Peter Maydell
2018-03-06 10:24 ` Kevin Wolf [this message]
2018-03-06 10:29 ` Peter Maydell
2018-03-06 12:12 ` Peter Maydell
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=20180306102404.GB7139@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).