public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Johanson <latexer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Keys and words: ways to fail your team
Date: Tue, 28 Jun 2005 16:09:33 -0700	[thread overview]
Message-ID: <20050628230932.GC17821@butchest.cubesearch.com> (raw)
In-Reply-To: <42C1D221.6070407@gentoo.org>

On Tue, Jun 28, 2005 at 03:41:37PM -0700, Ilya A. Volynets-Evenbakh wrote:
> Comrades!
> 
> Once more, I come before you with sad tidings. Evil anti-gentoo
> conspirators are plotting to destroy our
> wonderful distribution. Yet again they tried to subvert quality and
> integrity of our distribution by falsely
> claiming that certain packages build and run *gasp* stable *gasp* on
> platforms said saboteurs apparently
> do not even have access to.
> 
> This time many packages in dev-dotnet were marked testing / stable on
> all arches, but thanks to the
> valiant struggles of our tireless arch teams, at least SPARC and MIPS
> have now been rescued from the
> iniquity of the apostate traitors on the x86 monoarchist payroll. Other
> arches have also been warned, and
> hopefully will be in time to save themselves, or at least recover the
> damages in timely manner.
> 
> Comrades!
> 
> For how long will we tolerate these wreckers among us? How much more
> patience shall we show?
> It is about time to stop such behavior once and for all! Let us join
> against the forces of evil and deal
> it a crushing defeat!
> 
>     Death to vermin!

I know this is intended to be tongue in cheek, but I have a dev in the
dotnet herd who's really pretty upset right now as a result of such
apparently scathing comments accusing him of being an evil conspirator,
a wrecker, and traitor, when it wasn't even *him* who introduced the
keywords in question, he did a by the book bump moving arch -> ~arch for
all arches listed in keywords.

I understand that this is a consistent problem, and that we constantly
have to deal with breakages like this, but please don't send emails
like this with so many accusations without at least talking to the herd
lead, or viewing CVS history first.

I like dealing with the mess of pissed off and enflamed developers as
much as the arch teams like dealing with bad QA, so next time, please
use at least a *little* subtlty before blowing things up.

Anyway, I'm glad all the arch teams, who are the one's that never screw
up and save us all, are fixing things.

</sarcasm>

-pete


> 
> -- 
> gentoo-dev@gentoo.org mailing list
> 

-- 
Peter Johanson
<latexer@gentoo.org>
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-06-28 23:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28 22:41 [gentoo-dev] Keys and words: ways to fail your team Ilya A. Volynets-Evenbakh
2005-06-28 23:09 ` Peter Johanson [this message]
2005-06-28 23:30   ` Ilya A. Volynets-Evenbakh
2005-06-29  9:45     ` Chris Bainbridge
2005-06-29  9:53       ` Henrik Brix Andersen
2005-06-29 12:36       ` Mike Frysinger
2005-06-29 14:02     ` Chris Gianelloni

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=20050628230932.GC17821@butchest.cubesearch.com \
    --to=latexer@gentoo.org \
    --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