public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ilya A. Volynets-Evenbakh" <iluxa@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:30:12 -0700	[thread overview]
Message-ID: <42C1DD84.5040008@gentoo.org> (raw)
In-Reply-To: <20050628230932.GC17821@butchest.cubesearch.com>

Peter Johanson wrote:

>I know this is intended to be tongue in cheek,
>
Good.

> 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.
>  
>
Book in question sort of presumes that ones who change keywords
*personally* tested that package in question works. You set keyword,
you sign the life of your first-born that it will work. Or at least that's
the way it should be.

>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.
>  
>
This *is* a consistent problem. But it shouldn't be. QA. Should. Be. Done.

>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.
>  
>
Grow up people, I didn't even say names. To say more - I'm far more upset
about person who introduced keywords.

>Anyway, I'm glad all the arch teams, who are the one's that never screw
>up and save us all, are fixing things.
>  
>
Yeap. What would you do without us. At least I get yelled at only once for
technical mistakes I make.

></sarcasm>
>  
>
Oh, since we have to indicate jokes/sarcasm now:

LOPATA.


-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-06-28 23:33 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
2005-06-28 23:30   ` Ilya A. Volynets-Evenbakh [this message]
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=42C1DD84.5040008@gentoo.org \
    --to=iluxa@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