All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlo Arenas <carenas@gmail.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Stefan Hajnoczi" <stefanha@gmail.com>,
	qemu-devel@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
	"Liviu Ionescu" <ilg@livius.net>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Michal Suchánek" <msuchanek@suse.de>,
	"Aleksandar Markovic" <aleksandar.m.mail@gmail.com>
Subject: Re: [PATCH] configure: warn if not using a separate build directory
Date: Tue, 31 Mar 2020 20:03:58 -0700	[thread overview]
Message-ID: <CAPUEspgRLAyM21h3XaGurncJq9oDCGPAQ8S6zJTwdA31a3fFrg@mail.gmail.com> (raw)
In-Reply-To: <20200331103758.370644-1-berrange@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 266 bytes --]

On Tue, Mar 31, 2020 at 3:38 AM Daniel P. Berrangé <berrange@redhat.com>
wrote:

> Running configure directly from the source directory is a build
> configuration that will go away in future. It is also not currently
>

s/in future/in the future/g

Carlo

[-- Attachment #2: Type: text/html, Size: 562 bytes --]

      parent reply	other threads:[~2020-04-01  3:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 10:37 [PATCH] configure: warn if not using a separate build directory Daniel P. Berrangé
2020-03-31 11:11 ` Philippe Mathieu-Daudé
2020-03-31 11:41   ` Daniel P. Berrangé
2020-03-31 12:56     ` Philippe Mathieu-Daudé
2020-03-31 14:44 ` Eric Blake
2020-03-31 14:56   ` Daniel P. Berrangé
2020-03-31 15:51     ` Kevin Wolf
2020-03-31 15:10   ` BALATON Zoltan
2020-04-01  3:03 ` Carlo Arenas [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=CAPUEspgRLAyM21h3XaGurncJq9oDCGPAQ8S6zJTwdA31a3fFrg@mail.gmail.com \
    --to=carenas@gmail.com \
    --cc=aleksandar.m.mail@gmail.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=ilg@livius.net \
    --cc=kwolf@redhat.com \
    --cc=msuchanek@suse.de \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.