qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Patrick Venture <venture@google.com>
Cc: pbonzini@redhat.com, marcandre.lureau@redhat.com,
	berrange@redhat.com, philmd@linaro.org, qemu-devel@nongnu.org,
	Nabih Estefan <nabihestefan@google.com>
Subject: Re: [PATCH] scripts: dump stdin on meson-buildoptions error
Date: Fri, 28 Feb 2025 11:26:12 +0100	[thread overview]
Message-ID: <20250228102611.867231-2-pbonzini@redhat.com> (raw)
In-Reply-To: <20250227180454.2006757-1-venture@google.com>

> Dump sys.stdin when it errors on meson-buildoptions.py, letting us debug
> the build errors instead of just saying "Couldn't parse"

Sure, why not. :)  Queued the patch, it should go into 10.0.

Paolo



  reply	other threads:[~2025-02-28 10:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 18:04 [PATCH] scripts: dump stdin on meson-buildoptions error Patrick Venture
2025-02-28 10:26 ` Paolo Bonzini [this message]
2025-02-28 18:17   ` Patrick Venture

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=20250228102611.867231-2-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=nabihestefan@google.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=venture@google.com \
    /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).