From: Michael Tokarev <mjt@tls.msk.ru>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial <qemu-trivial@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] typedefs: Put them back into alphabetical order
Date: Sun, 29 Nov 2015 13:51:55 +0300 [thread overview]
Message-ID: <565AD8CB.7030305@msgid.tls.msk.ru> (raw)
In-Reply-To: <1447936168-9808-1-git-send-email-armbru@redhat.com>
19.11.2015 15:29, Markus Armbruster wrote:
> "Please keep this list in alphabetical order" has been more honoured
> in the breach than in the observance. Clean up.
>
> While there, drop a redundant struct declaration.
Applied to -trivial, thank you!
/mjt
prev parent reply other threads:[~2015-11-29 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 12:29 [Qemu-devel] [PATCH] typedefs: Put them back into alphabetical order Markus Armbruster
2015-11-19 13:03 ` Dr. David Alan Gilbert
2015-11-19 13:10 ` Daniel P. Berrange
2015-11-19 21:29 ` Eric Blake
2015-11-24 14:40 ` Markus Armbruster
2015-11-29 10:51 ` Michael Tokarev [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=565AD8CB.7030305@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).