From: Alin Nastac <mrness@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Please follow keywording policy
Date: Thu, 10 Mar 2005 10:07:46 +0200 [thread overview]
Message-ID: <42300052.1060102@gentoo.org> (raw)
In-Reply-To: <20050310005515.GA9129@cerberus.oppresses.us>
[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]
Jon Portnoy wrote:
>On Wed, Mar 09, 2005 at 08:56:51PM +0200, Alin Nastac wrote:
>
>
>>Ciaran McCreesh wrote:
>>
>>
>>
>>>Stick out a request on -dev. I bet someone here has a dsl device...
>>>
>>>
>>>
>>>
>>Okay, I buy it.
>>
>>a) Devs, who has a fcdsl, fcdsl2, fcdslsl, fcdslusb and/or fcdslslusb
>>(AVM FRITZ!Card DSL)? Step up and take net-dialup/fcdsl under your wing!
>>b) Who has a device that works with net-dialup/hcfusbmodem and is
>>willing to become its maintainer?
>>c)...
>>
>>In fact, who has any device that would work with some driver from
>>net-dialup? I don't have _any_ device at all!
>>
>>
>>
>
>Then how can we know anything in net-dialup actually works? Sounds like
>net-dialup is sorely lacking devs with the relevant hardware.
>
>
>
Well, judging after bugzilla, I would say that all my ebuilds works (or
have worked when I've submitted them). When I've become member in
net-dialup team, net-dialup had over 80 opened bugs, and this after I
solved a few dozens in my trial period.
Does any dev has any complaints about my work? I think not.
You wanna increase "quality" of ebuilds by taking net-dialup from me?
Okay, let the bugs pile up again!
Does any of the QA supporters looked at
http://bugs.gentoo.org/reports.cgi?product=Gentoo+Linux&datasets=NEW%3A&datasets=ASSIGNED%3A&datasets=REOPENED%3A
?
Gentoo isn't politics is getting the things done. At least this is my view.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-03-10 8:07 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
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 [this message]
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=42300052.1060102@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