From: Peter Maydell <peter.maydell@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/3] Error reporting patches for 2016-02-09
Date: Tue, 9 Feb 2016 17:44:52 +0000 [thread overview]
Message-ID: <CAFEAcA-dEuEjdZW0ke_ZrvMRK79MThmUz8Ms2fUT0UJ1kBh6dw@mail.gmail.com> (raw)
In-Reply-To: <1455024358-31133-1-git-send-email-armbru@redhat.com>
On 9 February 2016 at 13:25, Markus Armbruster <armbru@redhat.com> wrote:
> The following changes since commit e4a096b1cd4350eeca5dcdc391ab333d2083d7fd:
>
> ui/cocoa.m: Include qemu/osdep.h (2016-02-08 13:14:40 +0000)
>
> are available in the git repository at:
>
> git://repo.or.cz/qemu/armbru.git tags/pull-error-2016-02-09
>
> for you to fetch changes up to d76a3bf5c46d9e981faf09e6194c795ee54e5ae4:
>
> HACKING: Add a section on error handling and reporting (2016-02-09 13:19:49 +0100)
>
> ----------------------------------------------------------------
> Error reporting patches for 2016-02-09
>
> ----------------------------------------------------------------
> Markus Armbruster (3):
> Use error_fatal to simplify obvious fatal errors (again)
> error: Improve documentation some more
> HACKING: Add a section on error handling and reporting
>
Applied, thanks.
-- PMM
prev parent reply other threads:[~2016-02-09 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 13:25 [Qemu-devel] [PULL 0/3] Error reporting patches for 2016-02-09 Markus Armbruster
2016-02-09 13:25 ` [Qemu-devel] [PULL 1/3] Use error_fatal to simplify obvious fatal errors (again) Markus Armbruster
2016-02-09 13:25 ` [Qemu-devel] [PULL 2/3] error: Improve documentation some more Markus Armbruster
2016-02-09 13:25 ` [Qemu-devel] [PULL 3/3] HACKING: Add a section on error handling and reporting Markus Armbruster
2016-02-09 17:44 ` Peter Maydell [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=CAFEAcA-dEuEjdZW0ke_ZrvMRK79MThmUz8Ms2fUT0UJ1kBh6dw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=armbru@redhat.com \
--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.