public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alin Nastac <mrness@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Please follow keywording policy
Date: Wed, 09 Mar 2005 16:50:22 +0200	[thread overview]
Message-ID: <422F0D2E.1040301@gentoo.org> (raw)
In-Reply-To: <422EFCA6.2010607@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2568 bytes --]

Stephen P. Becker wrote:

> Alin Nastac wrote:
>
>> I didn't dropped any keywords yet but I've been pretty close to that. 
>> See http://bugs.gentoo.org/show_bug.cgi?id=81702 for more info.
>
>
> Congratulations, you just took something that pissed you off 
> personally and threw it up on the dev mailing list for the purpose of 
> attempting to make a point where there is none.  Never mind that for 
> well over a week, you joined #gentoo-mips at least 6 hours before any 
> of us in there would even be awake, said only "mips team ping", and 
> then logged off 5 minutes later.  You should have at least talked 
> directly to somebody before getting so pissed off.  Remember, when 
> *you* want something, *we're* not likely to come track you down.
>
Ok, I could understand that none of the mips team are online when I 
want, but how about the bug mentioned above? One month I 
waited/begged/threat!!! For what? For some lousy script updates, which 
is not arch dependent anyway!


>> C'mon people, how hard can it be to see if it builds right on your arch?
>
>
> So you are suggesting that we should mark something stable if it 
> simply compiles?  I really hope you don't apply this lazy method of QA 
> to everything you maintain, else I fear for the users installing those 
> packages.  This is the main reason we didn't touch that package, 
> because none of us had the ability to test pppoe.  If you had actually 
> made an attempt to talk to one of us when we were awake before running 
> your mouth, you would have known this.  In fact, we probably would 
> have just given you permission to remove the keyword assuming that no 
> repoman breakage resulted.
>
Not every package that I maintain is tested by me! How can I test a dsl 
driver when I have no such device!
I apply the good old rule that if a package has no open bugs for a 
month, it will be marked as stable.

If I would do things you way, in this moment net-dialup would have at 
least 100 opened bugs with no one carrying about them. I urge you to 
look in bugzilla to see how many rightfully complaints are there 
regarding my work. Not as if I consider less about a dev who made a 
mistake (only who do nothing, does no mistakes)...

It is OK to want to make more than a simple compile test, but from this 
to doing nothing when a fellow dev ask you to IS a big distance! A 
convenient excuse, nothing more...

I didn't wanted to get so involved in this bug, but invalid bug reports 
started by the transition from -r2 are killing me. In rest, what do I 
care that your arch is outdated!


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2005-03-09 15:32 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  1:55 [gentoo-dev] Please follow keywording policy Jason Wever
2005-03-09  2:00 ` Hasan Khalil
2005-03-09  7:38 ` Alin Nastac
2005-03-09 13:39   ` Stephen P. Becker
2005-03-09 14:50     ` Alin Nastac [this message]
2005-03-09 16:22       ` Ciaran McCreesh
2005-03-09 17:38         ` Alin Nastac
2005-03-09 18:38           ` Ciaran McCreesh
2005-03-09 18:56             ` Alin Nastac
2005-03-09 19:10               ` Stefan Schweizer
2005-03-09 19:10                 ` Stefan Schweizer
2005-03-09 21:30                 ` Luis F. Araujo
2005-03-09 22:57                 ` Alin Nastac
2005-03-09 23:27                   ` Stephen P. Becker
2005-03-10  0:50                     ` Donnie Berkholz
2005-03-10  0:18                       ` Daniel Goller
2005-03-09 23:36                   ` Jason Wever
2005-03-09 23:42                   ` Aron Griffis
2005-03-10  7:54                     ` Alin Nastac
2005-03-10  8:27                       ` Ciaran McCreesh
2005-03-10 15:54                         ` Chris Gianelloni
2005-03-10 15:52                       ` Chris Gianelloni
2005-03-10  4:34                   ` Grant Goodyear
2005-03-10  8:36                     ` Alin Nastac
2005-03-10 13:14                       ` Ciaran McCreesh
2005-03-10 16:00                       ` Chris Gianelloni
2005-03-10 19:00                         ` Alin Nastac
2005-03-10 19:33                           ` Chris Gianelloni
2005-03-10 21:25                             ` John Myers
2005-03-10 15:38                   ` Chris Gianelloni
2005-03-09 19:18               ` Patrick Lauer
2005-03-09 19:43                 ` Stefan Schweizer
2005-03-09 19:56                   ` Patrick Lauer
2005-03-10  0:55               ` Jon Portnoy
2005-03-10  8:07                 ` Alin Nastac
2005-03-09 19:20             ` Chris Gianelloni
2005-03-09 16:37       ` Stephen P. Becker
2005-03-09 16:43   ` Chris Gianelloni
2005-03-09 17:40     ` Alin Nastac

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=422F0D2E.1040301@gentoo.org \
    --to=mrness@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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