From: Laszlo Ersek <lersek@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v2] scripts/git.orderfile: Display meson files along with buildsys ones
Date: Tue, 8 Sep 2020 12:02:24 +0200 [thread overview]
Message-ID: <bd658d44-d9bd-81d1-f3c7-89c0d61f6dd2@redhat.com> (raw)
In-Reply-To: <20200907161222.41915-1-philmd@redhat.com>
On 09/07/20 18:12, Philippe Mathieu-Daudé wrote:
> Since commit a56650518f5 ("configure: integrate Meson in the build
> system") we replaced many Makefile by Meson files. Adapt the
> git.orderfile script to display the new file at the same position.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> scripts/git.orderfile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/scripts/git.orderfile b/scripts/git.orderfile
> index 73fd818d7f3..a021afc2d51 100644
> --- a/scripts/git.orderfile
> +++ b/scripts/git.orderfile
> @@ -18,6 +18,7 @@ docs/*
> configure
> Makefile*
> *.mak
> +meson.build
>
> # qapi schema
> qapi/*.json
>
Possibly related (not sure if there's another patch pending for it
already): if you run a "make clean" in the source tree, and have the
Meson submodule initialized, the "make clean" will delete files from the
Meson submodule.
find . \( -name '*.so' -o -name '*.dll' -o -name '*.[oda]' \) -type f \
"*.d" matches various meson files.
(Again, apologies if this is already known; I understand this is
probably the worst context to report his in...)
Thanks
Laszlo
next prev parent reply other threads:[~2020-09-08 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 16:12 [PATCH v2] scripts/git.orderfile: Display meson files along with buildsys ones Philippe Mathieu-Daudé
2020-09-08 9:17 ` Stefano Garzarella
2020-09-08 10:02 ` Laszlo Ersek [this message]
2020-09-08 11:48 ` Paolo Bonzini
2020-09-08 12:30 ` Laszlo Ersek
2020-09-12 6:01 ` Paolo Bonzini
2020-09-16 9:17 ` Laurent Vivier
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=bd658d44-d9bd-81d1-f3c7-89c0d61f6dd2@redhat.com \
--to=lersek@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).