qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Laszlo Ersek" <lersek@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH v2] scripts/git.orderfile: Display meson files along with buildsys ones
Date: Tue, 8 Sep 2020 13:48:53 +0200	[thread overview]
Message-ID: <79de1ef4-6e08-6f1c-030e-f40e7410e06c@redhat.com> (raw)
In-Reply-To: <bd658d44-d9bd-81d1-f3c7-89c0d61f6dd2@redhat.com>

On 08/09/20 12:02, Laszlo Ersek wrote:
> 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...)

Is this running "make clean" from an old commit (i.e. as in an in-tree
build) after having checked out the meson submodule?

Paolo



  reply	other threads:[~2020-09-08 11:49 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
2020-09-08 11:48   ` Paolo Bonzini [this message]
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=79de1ef4-6e08-6f1c-030e-f40e7410e06c@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=lersek@redhat.com \
    --cc=marcandre.lureau@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).