All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Smith <brad@comstyle.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Markus Armbruster <armbru@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Riku Voipio <riku.voipio@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU build broken
Date: Sat, 10 May 2014 20:22:03 -0400	[thread overview]
Message-ID: <536EC2AB.3030701@comstyle.com> (raw)
In-Reply-To: <536DD034.3060705@redhat.com>

On 10/05/14 3:07 AM, Paolo Bonzini wrote:
> Il 10/05/2014 08:45, Brad Smith ha scritto:
>>>
>>> Having your feature in-tree is a privilege, not a right.  You earn it by
>>> helping to maintain it.  "it's not really maintained right now" means it
>>> has not been earning its keep.  You're encouraged to remedy that.
>>
>> Huh? "my feature"? I have nothing to do with this. What kind of crazy
>> is this? How to misdirect and not take responsibility for breaking
>> something. If there wasn't sloppy irresponsible development in the
>> first place it wouldn't be an issue.
>
> Brad,
>
> all this is doing, is convincing people that bsd-user is not worth
> keeping in the tree.  It's a fact that in a million-line codebase not
> all patches can be tested by all people.

My posts have nothing to do with bsd-user. I don't give a shit about it.
The real issue is the process and the fact that someone removed a 
constant from the configure script and didn't even grep the tree to see
if it existed anywhere else. That is very sloppy.

> Why don't you send a patch instead of whining?

Constantly trying to deflect from the real issues.


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

  parent reply	other threads:[~2014-05-11  0:23 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
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 [this message]
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=536EC2AB.3030701@comstyle.com \
    --to=brad@comstyle.com \
    --cc=armbru@redhat.com \
    --cc=pbonzini@redhat.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 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.