qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 0/2] Error reporting patches for 2020-10-09
Date: Fri, 9 Oct 2020 15:47:46 +0100	[thread overview]
Message-ID: <CAFEAcA-snMmt1XBeJymUHcj+dc4fySZyU05BQKxL-oXA-r-qTQ@mail.gmail.com> (raw)
In-Reply-To: <20201009064858.323624-1-armbru@redhat.com>

On Fri, 9 Oct 2020 at 07:49, Markus Armbruster <armbru@redhat.com> wrote:
>
> The following changes since commit 497d415d76b9f59fcae27f22df1ca2c3fa4df64e:
>
>   Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20201008-1' into staging (2020-10-08 21:41:20 +0100)
>
> are available in the Git repository at:
>
>   git://repo.or.cz/qemu/armbru.git tags/pull-error-2020-10-09
>
> for you to fetch changes up to 805d44961b9015716cc13c1d3e49457af3970d82:
>
>   error: Use error_fatal to simplify obvious fatal errors (again) (2020-10-09 08:36:23 +0200)
>
> ----------------------------------------------------------------
> Error reporting patches for 2020-10-09
>
> ----------------------------------------------------------------
> Markus Armbruster (2):
>       error: Remove NULL checks on error_propagate() calls (again)
>       error: Use error_fatal to simplify obvious fatal errors (again)


Applied, thanks.

Please update the changelog at https://wiki.qemu.org/ChangeLog/5.2
for any user-visible changes.

-- PMM


      parent reply	other threads:[~2020-10-09 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09  6:48 [PULL 0/2] Error reporting patches for 2020-10-09 Markus Armbruster
2020-10-09  6:48 ` [PULL 1/2] error: Remove NULL checks on error_propagate() calls (again) Markus Armbruster
2020-10-09  9:43   ` Jens Freimann
2020-10-09  6:48 ` [PULL 2/2] error: Use error_fatal to simplify obvious fatal errors (again) Markus Armbruster
2020-10-09 14:47 ` 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-snMmt1XBeJymUHcj+dc4fySZyU05BQKxL-oXA-r-qTQ@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 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).