From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Thomas Huth <thuth@redhat.com>
Subject: Re: [RFC PATCH] Makefile: include gtags in UNCHECKED_GOALS
Date: Thu, 11 May 2023 18:14:27 +0100 [thread overview]
Message-ID: <87pm76yemd.fsf@linaro.org> (raw)
In-Reply-To: <CABgObfabZgJro_faUfhADWtTg1ewpM2iMtmt4KkJpSBqmJsF_Q@mail.gmail.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> Il gio 11 mag 2023, 18:56 Alex Bennée <alex.bennee@linaro.org> ha scritto:
>
> This is the mechanism we use to avoid defaulting to a build dir when
> we don't need to.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> I had already squashed this into Steven Sistare's recently posted patch, which otherwise would have broken the
> "pages" job in CI.
\o/
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2023-05-11 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 16:56 [RFC PATCH] Makefile: include gtags in UNCHECKED_GOALS Alex Bennée
2023-05-11 17:02 ` Paolo Bonzini
2023-05-11 17:14 ` Alex Bennée [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=87pm76yemd.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).