From: Cornelia Huck <cohuck@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Eric Farman <farman@linux.vnet.ibm.com>,
Thomas Huth <thuth@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH for-2.10 0/1] Fix "make clean" for s390 target
Date: Tue, 15 Aug 2017 13:07:16 +0200 [thread overview]
Message-ID: <20170815130716.296f031c.cohuck@redhat.com> (raw)
In-Reply-To: <CAFEAcA8=_1exzxHEOvmFV1r_oxaGi7beeCVzy=bvVx8tQTNU8w@mail.gmail.com>
On Tue, 15 Aug 2017 11:00:51 +0100
Peter Maydell <peter.maydell@linaro.org> wrote:
> On 14 August 2017 at 21:44, Eric Farman <farman@linux.vnet.ibm.com> wrote:
> > How often does one really do a "make clean" ? Rather infrequently,
> > as I only stumbled on this today.
>
> FWIW, one of my standard pre-merge build tests does a
> "make clean" and then a make (mostly as a check that we
> do build from clean as well as incrementally). Not sure
> why it didn't catch this...
Probably because you don't build on s390x... I'll add it to my
workflow, though.
next prev parent reply other threads:[~2017-08-15 11:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 20:44 [Qemu-devel] [PATCH for-2.10 0/1] Fix "make clean" for s390 target Eric Farman
2017-08-14 20:44 ` [Qemu-devel] [PATCH 1/1] pc-bios/s390-ccw: Use rm command during make clean Eric Farman
2017-08-15 7:23 ` Cornelia Huck
2017-08-15 5:02 ` [Qemu-devel] [PATCH for-2.10 0/1] Fix "make clean" for s390 target Thomas Huth
2017-08-15 7:03 ` Cornelia Huck
2017-08-15 8:01 ` Thomas Huth
2017-08-15 8:26 ` Thomas Huth
2017-08-15 8:32 ` Cornelia Huck
2017-08-15 8:39 ` Thomas Huth
2017-08-15 10:27 ` Eric Farman
2017-08-15 10:00 ` Peter Maydell
2017-08-15 11:07 ` Cornelia Huck [this message]
2017-08-15 11:10 ` Peter Maydell
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=20170815130716.296f031c.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=farman@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--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).