From: foser <foser@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Ebuild bumping policy wrt KEYWORDS
Date: Wed, 01 Sep 2004 12:06:59 +0200 [thread overview]
Message-ID: <1094033220.9970.17.camel@rivendell> (raw)
In-Reply-To: <41352F55.2010107@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2585 bytes --]
On Tue, 2004-08-31 at 22:09 -0400, Travis Tilley wrote:
> if by bugged you mean versions that work?
I think you mean 'versions that run with known bugs' ? Still bugged I'm
afraid.
> > I find it ironic that you who are so keen on pointing out that something
> > was broken in x86 gnome and obviously knew about it all this time,
> > failed to inform us during that period.
>
> there was an open bug report. would you have liked us to file duplicates?
It wasn't open all the time & no i was talking about 'mailing' or maybe
poking on IRC. Note that I myself was unavailable during this period.
Besides the bug in question got fixed in a day, so before that point
there's still an unexplained gap ? And you obviously knew about it,
because you already had marked it stable...
> > I'd appreciate it if you guys stopped distorting the facts to
> > consolidate your own QA-hurting policy of moving beyond the maintainers
>
> who are you to talk about QA hurting? just take a look at:
> http://bugs.gentoo.org/show_bug.cgi?id=24439
>
> you even have the portage devs screaming at you there.
A nice misinterpretation, once again you try to play it on the person &
on a totally unrelated example, while I even told you thats sort of a
weak way to go about arguing your case (you don't have much else i
guess). Maybe if you read it objectively, you would would be able to
give a fair judgement, but i guess thats way beyond you.
Basically what you are saying here comes down to this : "Judge, they
steal too, so I should be allowed to steal as well.." I don't think that
holds up anywhere.
Anyway, were open to changes there, unlike some devs here.
> well i'm pretty sure i shouldnt be taking QA advice from the gnome team.
> that and the bug i mention is quite an interesting read. i'd say my case
> for not paying attention to a single word you say would indeed be quite
> strong.
Again on the person, you really don't have any objective, sound
arguments do you ?
Well I'd say that it doesn't really matter, because in the end it is not
your decision and I know most devs are more objective than you in this
matter. I actually do not think I can convince you of anything because
you are so stuck up in your own way of thinking. Thats exactly what this
is about, because if you would be reasonable then this wouldn't be an
issue in the first place. You are afraid of losing some of the freedom
you enjoy now and won't trade it for better QA, it's very human to hang
on to every scrap of imagined power you got.
- foser
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-01 10:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 1:11 [gentoo-dev] Ebuild bumping policy wrt KEYWORDS Jason Wever
2004-08-25 3:00 ` Jason Wever
2004-08-25 15:30 ` Michael Kohl
2004-08-26 3:17 ` Jason Wever
2004-08-26 14:51 ` Carsten Lohrke
2004-08-26 15:04 ` Ciaran McCreesh
2004-08-26 15:30 ` Carsten Lohrke
2004-08-26 15:33 ` Ciaran McCreesh
2004-08-26 16:11 ` Travis Tilley
2004-08-31 13:07 ` foser
2004-09-01 2:09 ` Travis Tilley
2004-09-01 10:06 ` foser [this message]
2004-09-01 16:30 ` Robert Moss
2004-09-01 23:15 ` Carsten Lohrke
2004-09-01 23:20 ` Ciaran McCreesh
2004-09-01 23:42 ` Carsten Lohrke
2004-08-26 16:27 ` Carsten Lohrke
2004-08-31 13:23 ` foser
2004-08-25 13:51 ` Chris Gianelloni
2004-08-26 3:22 ` Jason Wever
2004-08-26 4:49 ` Donnie Berkholz
2004-08-26 5:20 ` Jason Wever
2004-08-26 6:19 ` Donnie Berkholz
2004-08-26 14:16 ` Chris Gianelloni
2004-08-26 14:44 ` Ciaran McCreesh
2004-08-26 15:02 ` Chris Gianelloni
2004-08-26 15:31 ` Jason Wever
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=1094033220.9970.17.camel@rivendell \
--to=foser@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