From: Markus Armbruster <armbru@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>, "John Snow" <jsnow@redhat.com>
Subject: Re: [PATCH 4/5] python: add .gitignore
Date: Wed, 28 Oct 2020 10:16:33 +0100 [thread overview]
Message-ID: <871rhi1zim.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <f9ea6ce1-f464-0376-29ac-6071f680e63b@redhat.com> (Thomas Huth's message of "Wed, 28 Oct 2020 09:13:10 +0100")
Thomas Huth <thuth@redhat.com> writes:
> On 27/10/2020 23.38, John Snow wrote:
>> Ignore build and package output (build, dist, qemu.egg-info);
>> effectively these are "in-tree" builds of a kind.
>
> Since we recently moved away from in-tree builds, could these also be made
> out-of-tree only?
The build should only write to the per-build spaces: the build tree,
per-build scratch in /tmp, ... Writing to shared space such as the
source tree can break parallel independent builds. I consider that a
bug.
next prev parent reply other threads:[~2020-10-28 9:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 22:38 [PATCH 0/5] python: add linters to gitlab CI John Snow
2020-10-27 22:38 ` [PATCH 1/5] python: add pytest and tests John Snow
2020-10-28 6:19 ` Thomas Huth
2020-10-28 13:23 ` John Snow
2020-10-28 14:09 ` Philippe Mathieu-Daudé
2020-10-28 14:54 ` Thomas Huth
2020-10-28 18:38 ` John Snow
2020-10-27 22:38 ` [PATCH 2/5] python: add excluded dirs to flake8 config John Snow
2020-10-28 8:50 ` Philippe Mathieu-Daudé
2020-10-28 13:42 ` John Snow
2020-10-27 22:38 ` [PATCH 3/5] python: add Makefile for some common tasks John Snow
2020-10-27 22:38 ` [PATCH 4/5] python: add .gitignore John Snow
2020-10-28 8:13 ` Thomas Huth
2020-10-28 9:16 ` Markus Armbruster [this message]
2020-10-28 9:22 ` Daniel P. Berrangé
2020-10-28 13:39 ` John Snow
2020-10-28 13:41 ` Daniel P. Berrangé
2020-10-28 13:26 ` John Snow
2020-10-28 18:33 ` John Snow
2020-10-27 22:38 ` [PATCH 5/5] gitlab: add python linters to CI John Snow
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=871rhi1zim.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@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 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.