From: John Snow <jsnow@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Fam Zheng" <fam@euphon.net>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tests/vm: remove unused --target-list option
Date: Tue, 17 Sep 2019 15:52:51 -0400 [thread overview]
Message-ID: <087d7f29-7935-f2a4-cac7-5c0210d067a6@redhat.com> (raw)
In-Reply-To: <87a7b2201l.fsf@linaro.org>
On 9/17/19 3:30 PM, Alex Bennée wrote:
>
> John Snow <jsnow@redhat.com> writes:
>
>> On 9/17/19 2:58 PM, Alex Bennée wrote:
>>>
>>> John Snow <jsnow@redhat.com> writes:
>>>
>>>> It's not used; so remove the distraction.
>>>
>>> It's a developer feature so you can run specific builds against the VM
>>> images. I certainly have used it, unless you are saying it's broken now?
>>>
>>
>> What consumes it? I can't find where it *does* something:
>
> It's past as the rest:
>
> -- \ <- all args after this
> $(if $(TARGET_LIST),--target-list=$(TARGET_LIST)) \
> $(if $(EXTRA_CONFIGURE_OPTS),$(EXTRA_CONFIGURE_OPTS)), \
>
> Become argv in:
>
> args, argv = parse_args(vmcls)
> ...
> cmd = [vm.BUILD_SCRIPT.format(
> configure_opts = " ".join(argv),
> jobs=int(args.jobs),
> target=args.build_target,
> verbose = "V=1" if args.verbose else "")]
>
augh, optparse ... okay, I goofed. I didn't realize they come back
unparsed. So they become configure options specifically, OK, got it.
Disregard, sorry!
NACK
--js
prev parent reply other threads:[~2019-09-17 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 18:49 [Qemu-devel] [PATCH] tests/vm: remove unused --target-list option John Snow
2019-09-17 18:58 ` Alex Bennée
2019-09-17 19:00 ` John Snow
2019-09-17 19:30 ` Alex Bennée
2019-09-17 19:52 ` John Snow [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=087d7f29-7935-f2a4-cac7-5c0210d067a6@redhat.com \
--to=jsnow@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=philmd@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).