From: Steven Sistare <steven.sistare@oracle.com>
To: "Markus Armbruster" <armbru@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dave@treblig.org>,
Jason Wang <jasowang@redhat.com>,
Michael Roth <michael.roth@amd.com>, Peter Xu <peterx@redhat.com>,
Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH v6 0/5] string list functions
Date: Tue, 27 Feb 2024 10:37:53 -0500 [thread overview]
Message-ID: <f27bc152-371b-405c-9c48-994cf3c928a0@oracle.com> (raw)
In-Reply-To: <874jduapug.fsf@pond.sub.org>
On 2/27/2024 10:28 AM, Markus Armbruster wrote:
> Philippe Mathieu-Daudé <philmd@linaro.org> writes:
>
>> Hi Markus,
>>
>> Here are the patches I queued until you told me you'd
>> object to the CamelCase filename strList.[ch].
>>
>> Steve, please take over ;)
>
> I'm going to post the part of the series I'm ready to queue as v7, with
> minor modifications:
>
> * Rename strv_from_strList() to strv_from_str_list(), and put it into
> qapi/qapi-type-helpers.c.
>
> * Tweak its function comment.
>
> * Rename its local variable @argv to @strv.
>
> * Cosmetic commit message tweaks.
>
> We can then talk about the remainder.
Thanks Markus, that saves some time and email.
- Steve
prev parent reply other threads:[~2024-02-27 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 14:11 [PATCH v6 0/5] string list functions Philippe Mathieu-Daudé
2024-02-26 14:11 ` [PATCH v6 1/5] util: str_split Philippe Mathieu-Daudé
2024-02-26 14:11 ` [PATCH v6 2/5] qapi: QAPI_LIST_LENGTH Philippe Mathieu-Daudé
2024-02-26 14:11 ` [PATCH v6 3/5] util: strv_from_strList Philippe Mathieu-Daudé
2024-02-26 14:11 ` [PATCH v6 4/5] util: strList unit tests Philippe Mathieu-Daudé
2024-02-26 14:11 ` [PATCH v6 5/5] migration: simplify exec migration functions Philippe Mathieu-Daudé
2024-02-26 14:47 ` [PATCH v6 0/5] string list functions Steven Sistare
2024-02-27 15:28 ` Markus Armbruster
2024-02-27 15:37 ` Steven Sistare [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=f27bc152-371b-405c-9c48-994cf3c928a0@oracle.com \
--to=steven.sistare@oracle.com \
--cc=armbru@redhat.com \
--cc=dave@treblig.org \
--cc=farosas@suse.de \
--cc=jasowang@redhat.com \
--cc=michael.roth@amd.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--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).