From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Weil <sw@weilnetz.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-trivial <qemu-trivial@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-trivial] [PATCH] misc: Use g_assert_not_reached for code which is expected to be unreachable
Date: Sat, 27 Jul 2013 11:21:10 +0400 [thread overview]
Message-ID: <51F374E6.2090708@msgid.tls.msk.ru> (raw)
In-Reply-To: <1374769288-19745-1-git-send-email-sw@weilnetz.de>
25.07.2013 20:21, Stefan Weil wrote:
> The macro g_assert_not_reached is a better self documenting replacement
> for assert(0) or assert(false).
Thanks, applied to the trivial patches queue.
/mjt
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Weil <sw@weilnetz.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-trivial <qemu-trivial@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] misc: Use g_assert_not_reached for code which is expected to be unreachable
Date: Sat, 27 Jul 2013 11:21:10 +0400 [thread overview]
Message-ID: <51F374E6.2090708@msgid.tls.msk.ru> (raw)
In-Reply-To: <1374769288-19745-1-git-send-email-sw@weilnetz.de>
25.07.2013 20:21, Stefan Weil wrote:
> The macro g_assert_not_reached is a better self documenting replacement
> for assert(0) or assert(false).
Thanks, applied to the trivial patches queue.
/mjt
next prev parent reply other threads:[~2013-07-27 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 16:21 [Qemu-trivial] [PATCH] misc: Use g_assert_not_reached for code which is expected to be unreachable Stefan Weil
2013-07-25 16:21 ` [Qemu-devel] " Stefan Weil
2013-07-27 7:21 ` Michael Tokarev [this message]
2013-07-27 7:21 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
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=51F374E6.2090708@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
/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.