public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Goller <morfic@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Please follow keywording policy
Date: Wed, 09 Mar 2005 18:18:04 -0600	[thread overview]
Message-ID: <422F923C.2000303@gentoo.org> (raw)
In-Reply-To: <422F99BD.8090509@gentoo.org>

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

Donnie Berkholz wrote:
> Stephen P. Becker wrote:
> | Nobody is asking you to drop your job.  However, what people are saying
> | is if you don't have hardware, then how can you properly maintain a
> | driver for it?  If I didn't have any mips machines, how could I be a
> | member of the mips team?  Instead of trying to maintain a bunch of
> | drivers that you can't test, why don't you recruit some more devs for
> | the dialup herd who do have such hardware?  You can create a team that
> | coordinates through you to ensure good QA for these drivers.
>
> There is a fairly common case that a package exists that Gentoo _should_
> have in the tree, but those people with the hardware are unable to
> become devs because of time commitments or other reasons. I see no
> reason a dev can't collaborate with a non-dev on testing packages.
--
gentoo-dev@gentoo.org mailing list

Amen to that.


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

  reply	other threads:[~2005-03-10  1:33 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 [this message]
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=422F923C.2000303@gentoo.org \
    --to=morfic@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