public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Removals reply (I am not going to figure out which tread of those all should i reply to)
Date: Fri, 01 Feb 2013 18:05:00 +0100	[thread overview]
Message-ID: <510BF5BC.9010009@flameeyes.eu> (raw)
In-Reply-To: <CA+NrkpfF0fu5Rx1LjsmVfttwN0BwOrFbOR90_o4gXRbq8qeTUw@mail.gmail.com>

On 01/02/2013 18:00, Tomáš Chvátal wrote:
> No, they won't get anyone looking over their shoulder unless they
> decide to neglect the bugs as few maintainers did.
> I didn't see a lot forced removals caused by qa, did you?

As far as I can tell, they come down to two:

 - webmin; which was saved after a masking and ended up not going
anywhere, as most of the bugs (most security-related due to the nature
of webmin!) were still around months after the unmask;

 - ${forgothename} which Robbins claimed he fixed in five minutes and
our QA was bad — where his fix was exchanging a build-time failure with
a runtime abort, and thus was kicked just as fine;

You could possibly add the damn squeezebox software that even Logitech
discontinued, but for that I'd just refer to the previous flame which
for my side boiled down "if you want to keep it around, mask the fucker
because it's crap".

-- 
Diego Elio Pettenò — Flameeyes
flameeyes@flameeyes.eu — http://blog.flameeyes.eu/


  reply	other threads:[~2013-02-01 17:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 13:53 [gentoo-dev] Removals reply (I am not going to figure out which tread of those all should i reply to) Tomáš Chvátal
2013-02-01 14:52 ` Rich Freeman
2013-02-01 17:00   ` Tomáš Chvátal
2013-02-01 17:05     ` Diego Elio Pettenò [this message]
2013-02-02 19:35 ` [gentoo-dev] Removals reply - please write adequate log messages! Andreas K. Huettel

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=510BF5BC.9010009@flameeyes.eu \
    --to=flameeyes@flameeyes.eu \
    --cc=gentoo-dev@lists.gentoo.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