Gentoo Archives: gentoo-user

From: Mark David Dumlao <madumlao@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Hard to find netiquette, enculturation bug. (Was: Re: [gentoo-user] GNOME: Cant logout and Lock Screen is showing different background from GNOME screensaver)
Date: Mon, 22 Dec 2008 14:51:34
Message-Id: 6e2210230812220651k4642b152ked959f637254e51c@mail.gmail.com
In Reply to: Re: [gentoo-user] Hard to find netiquette, enculturation bug. (Was: Re: [gentoo-user] GNOME: Cant logout and Lock Screen is showing different background from GNOME screensaver) by Volker Armin Hemmann
1 On Mon, Dec 22, 2008 at 10:02 PM, Volker Armin Hemmann
2 <volker.armin.hemmann@××××××××××××.de> wrote:
3 >> Please. He's completely right in demanding apologies and a swift
4 >> reaction to the problem -because if users cannot access the list due to
5 >> undocumented stuff, it's a problem.
6 >
7 > no, he is absolutly wrong in demanding everything. Nobody is paid to be here
8 > or answer his mails. He asked something nobody was able to or willing to
9 > answer. The html mails were a different problem. And now he thinks that his
10 > problem was caused by html - instead it was caused by a lack of
11 > knowledge/willingness in participation.
12 Guys I think you need to take a breather.
13
14 I didn't demand an apology.
15 I didn't even demand an answer.
16 Go look at the OP and the replies and take an objective look at the
17 words. Whatever the venomous, naggy, pompous, self-righteous - or even
18 injured - attitude it is you might be projecting just isn't present at
19 all.
20
21 I just said "hey, look around you guys, here's a problem, and here's
22 some proof that we have it." btw, why is it a problem? If I was just
23 as surprised at the unexpected tones of the responses then, I'm not
24 now. Whatever's been said has been said, and this is the Internet
25 after all.
26
27 If it explodes so quickly in everyone's face just to see an issue even
28 mentioned - then I'm apologizing on behalf of everyone. As far as I'm
29 concerned, the problem is identified and the obvious solution - some
30 subscription-level FAQ/warning - works and has already been suggested
31 to the bugs people. There's no need for the rest of this.

Replies