From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 00/40] Error reporting patches for 2018-10-22
Date: Wed, 24 Oct 2018 06:10:24 +0200 [thread overview]
Message-ID: <877ei856j3.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CAFEAcA9Ob=W85L2wwPisS5p+k9Ah3V_mni3D-ociz-uf2nqL8A@mail.gmail.com> (Peter Maydell's message of "Tue, 23 Oct 2018 19:59:39 +0100")
Peter Maydell <peter.maydell@linaro.org> writes:
> On 23 October 2018 at 14:04, Markus Armbruster <armbru@redhat.com> wrote:
>> The following changes since commit b312532fd03413d0e6ae6767ec793a3e30f487b8:
>>
>> Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2018-10-19 19:01:07 +0100)
>>
>> are available in the Git repository at:
>>
>> git://repo.or.cz/qemu/armbru.git tags/pull-error-2018-10-22-v2
>>
>> for you to fetch changes up to 70f81ac4800c5cf33415c966d63bf89af5cefbb9:
>>
>> error: Drop bogus "use error_setg() instead" admonitions (2018-10-23 14:48:32 +0200)
>>
>> ----------------------------------------------------------------
>> Error reporting patches for 2018-10-22
>>
>> * Replace some unwise uses of error_report() & friends
>> * Print error when using incorrect backend for debugcon
>>
>> ----------------------------------------------------------------
>> v2: Fix a stale sentence in commit message of PATCH 05/40.
>
> Sorry, I'd already pushed the merge of v1 to master before I saw this one.
No biggie. It was worth a try.
prev parent reply other threads:[~2018-10-24 4:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 13:04 [Qemu-devel] [PULL v2 00/40] Error reporting patches for 2018-10-22 Markus Armbruster
2018-10-23 13:04 ` [Qemu-devel] [PULL v2 05/40] block: Use warn_report() & friends to report warnings Markus Armbruster
2018-10-23 18:59 ` [Qemu-devel] [PULL v2 00/40] Error reporting patches for 2018-10-22 Peter Maydell
2018-10-24 4:10 ` Markus Armbruster [this message]
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=877ei856j3.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=peter.maydell@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.