From: Luiz Capitulino <lcapitulino@redhat.com>
To: Amos Kong <akong@redhat.com>
Cc: mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6 0/3] qapi: fix coding style in generated code
Date: Thu, 19 Jun 2014 10:40:36 -0400 [thread overview]
Message-ID: <20140619104036.74fa5f43@redhat.com> (raw)
In-Reply-To: <1402399553-21692-1-git-send-email-akong@redhat.com>
On Tue, 10 Jun 2014 19:25:50 +0800
Amos Kong <akong@redhat.com> wrote:
> Not a serious issue, but it's helpful if we can fix it.
Applied to the qmp branch, thanks.
>
> V2: split change of scripts/qapi-visit.py to a split patch,
> eat space by using a special char as Markus suggested
> V3: update commitlog, update special string, fix of adding
> const replace string by pattern
> V4: fix pattern to cleanup special string (Paolo)
> V5: fix string checking bug (Luiz), update commitlog (Eric)
> add comments for c_type() function
> V6: add is_c_ptr() and fix lost endswith (Markus)
>
> Amos Kong (3):
> qapi: fix coding style in parameters list
> qapi: add const prefix to 'char *' insider c_type()
> qapi: Suppress unwanted space between type and identifier
>
> scripts/qapi-commands.py | 8 +++-----
> scripts/qapi-visit.py | 20 ++++++++++----------
> scripts/qapi.py | 25 +++++++++++++++++++------
> 3 files changed, 32 insertions(+), 21 deletions(-)
>
prev parent reply other threads:[~2014-06-19 19:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 11:25 [Qemu-devel] [PATCH v6 0/3] qapi: fix coding style in generated code Amos Kong
2014-06-10 11:25 ` [Qemu-devel] [PATCH v6 1/3] qapi: fix coding style in parameters list Amos Kong
2014-06-10 11:25 ` [Qemu-devel] [PATCH v6 2/3] qapi: add const prefix to 'char *' insider c_type() Amos Kong
2014-06-18 3:51 ` Eric Blake
2014-06-18 7:54 ` Amos Kong
2014-06-10 11:25 ` [Qemu-devel] [PATCH v6 3/3] qapi: Suppress unwanted space between type and identifier Amos Kong
2014-06-19 14:40 ` Luiz Capitulino [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=20140619104036.74fa5f43@redhat.com \
--to=lcapitulino@redhat.com \
--cc=akong@redhat.com \
--cc=armbru@redhat.com \
--cc=mdroth@linux.vnet.ibm.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).