qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brad Smith <brad@comstyle.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Riku Voipio <riku.voipio@linaro.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU build broken
Date: Fri, 09 May 2014 19:49:40 -0400	[thread overview]
Message-ID: <536D6994.2090404@comstyle.com> (raw)
In-Reply-To: <CAFEAcA-1N1OxaeFmE6j98L7wbG5uJKhGPVjpJ6VUnk+R2_OMjw@mail.gmail.com>

On 09/05/14 7:35 PM, Peter Maydell wrote:
> On 10 May 2014 00:02, Brad Smith <brad@comstyle.com> wrote:
>> On 08/05/14 10:54 AM, Peter Maydell wrote:
>>> Ah, bsd-user. Do you actually use it, or is it just
>>> in the default compile that you're running?
>
>> I do not use it personally but it is common sense that commits
>> must not be breaking the build.
>
> I generally agree, but the minor ports (roughly, anything
> not x86 Linux) are inevitably going to get broken from time
> to time, because not everybody has access to all those
> systems to test on. bsd-user is particularly bad because
> it is a large chunk of code only built for BSD and it's
> not really maintained right now. (Hence my interest in
> whether it actually has users or if we're just carrying
> around a big lump of dead weight code.)

This is just excuses and points out poor project process.
There could easily be a staging branch to deal with this.

> If we had a system that automatically tested all pull
> requests on a full set of build systems and mailed the
> list with the results, that would be nice, but we don't...
>
> thanks
> -- PMM
>


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

  reply	other threads:[~2014-05-09 23:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 14:47 [Qemu-devel] QEMU build broken Brad Smith
2014-05-08 14:54 ` Peter Maydell
2014-05-09  8:57   ` Riku Voipio
2014-05-09  9:55     ` Peter Maydell
2014-05-09 17:26       ` Stacey Son
2014-05-09 23:02   ` Brad Smith
2014-05-09 23:35     ` Peter Maydell
2014-05-09 23:49       ` Brad Smith [this message]
2014-05-09 23:59         ` Peter Maydell
2014-05-10  6:25         ` Markus Armbruster
2014-05-10  6:45           ` Brad Smith
2014-05-10  7:07             ` Paolo Bonzini
2014-05-10  9:18               ` Peter Maydell
2014-05-11  0:22               ` Brad Smith
2014-05-12  9:13                 ` Markus Armbruster
  -- strict thread matches above, loose matches on Subject: below --
2014-03-16 13:22 Brad Smith
2014-03-16 13:26 ` Peter Maydell
2014-03-16 13:40   ` Marcel Apfelbaum
2014-03-16 14:33   ` Brad Smith
2014-03-16 15:03     ` Peter Maydell
2014-03-16 15:28       ` Brad Smith

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=536D6994.2090404@comstyle.com \
    --to=brad@comstyle.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@linaro.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).