public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aron Griffis <agriffis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] where goes Gentoo?
Date: Thu, 9 Jun 2005 00:52:35 -0400	[thread overview]
Message-ID: <20050609045235.GA5129@olive.flatmonk> (raw)
In-Reply-To: <42A766DA.70907@ieee.org>

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

Nathan L. Adams wrote:	[Wed Jun 08 2005, 05:44:58PM EDT]
> Using your list there would be two types of enterprise 'requirements':
> process requirements and support requirements.

Thanks for pointing that out.  I'm not good at seeing distinctions
like that.

> What developers seem to forget, is that they too are end-users. For
> instance, a particular developer's responsibilities may be
> Baselayout, Epm, Gentoo/Alpha, Gentoo/IA64, Keychain, Mozilla, Mutt,
> Vim, and such.  That makes him/her an end-user for everything else
> thats installed on their system. In other words, developers are just
> a subset of the user base.

Nah, I don't use any of that stuff.

Waaaiiit a minute, that list looks awful familiar...  ;-)

Regards,
Aron

--
Aron Griffis
Gentoo Linux Developer


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-06-09  4:37 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-06 23:55 [gentoo-dev] where goes Gentoo? Aron Griffis
2005-06-07  0:36 ` Colin Kingsley
2005-06-07 22:07   ` Chris Gianelloni
2005-06-07  1:02 ` Lance Albertson
2005-06-07 15:08   ` Aron Griffis
2005-06-07 16:23     ` Corey Shields
2005-06-07 17:56     ` Aron Griffis
2005-06-07 22:38       ` Chris Gianelloni
2005-06-07 22:57         ` Aron Griffis
2005-06-07 22:57         ` Corey Shields
2005-06-07  1:04 ` Dylan Carlson
2005-06-07  2:15   ` Alec Warner
2005-06-07  2:18 ` Corey Shields
2005-06-07  2:45   ` Collins Richey
2005-06-07  3:29     ` Dylan Carlson
2005-06-07  3:36       ` Mike Frysinger
2005-06-07  4:29         ` Dylan Carlson
2005-06-07  4:51 ` Greg KH
2005-06-07  5:19   ` Lance Albertson
2005-06-07  5:01 ` M. Edward (Ed) Borasky
2005-06-07  5:24   ` M. Edward (Ed) Borasky
2005-06-07  5:41 ` James Northrup
2005-06-07 12:14 ` Luca Barbato
2005-06-07 15:24 ` Simon Stelling
     [not found] ` <20050607183425.GA29735@xover.htu.tuwien.ac.at>
2005-06-07 19:18   ` Aron Griffis
2005-06-07 19:51     ` Haas Wernfried
2005-06-07 21:13 ` Maurice van der Pot
2005-06-07 22:05 ` Chris Gianelloni
2005-06-08  5:14   ` Alin Nastac
2005-06-08 13:40     ` Chris Gianelloni
2005-06-08 21:44 ` Nathan L. Adams
2005-06-09  4:52   ` Aron Griffis [this message]
2005-06-11 13:37 ` Chris White
2005-06-12 20:09   ` Athul Acharya
2005-06-12 20:33     ` Zac Medico
2005-06-13 11:18       ` Sami Samhuri
2005-06-16  5:33 ` [gentoo-dev] where goes Gentoo? Where went Fido? Jim Northrup
2005-06-16 16:47   ` Alec Warner
2005-08-03 11:55 ` [gentoo-dev] Re: where goes Gentoo? Sven Köhler
2005-08-03 13:39   ` Chris Gianelloni
2005-08-03 15:36     ` Duncan
2005-08-03 16:10       ` River Yan
2005-08-03 18:43     ` Sven Köhler
  -- strict thread matches above, loose matches on Subject: below --
2005-06-09 22:32 [gentoo-dev] " Stuart Herbert
2005-06-09 22:53 ` Aron Griffis
2005-06-10  8:28 ` Thierry Carrez

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=20050609045235.GA5129@olive.flatmonk \
    --to=agriffis@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