From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Re: enewuser/enewgroup getting their own eclass
Date: Wed, 23 Nov 2005 14:14:31 -0700 [thread overview]
Message-ID: <pan.2005.11.23.21.14.30.586966@cox.net> (raw)
In-Reply-To: 1132777755.27288.161.camel@cgianelloni.nuvox.net
Chris Gianelloni posted
<1132777755.27288.161.camel@cgianelloni.nuvox.net>, excerpted below, on
Wed, 23 Nov 2005 15:29:15 -0500:
> On Wed, 2005-11-23 at 13:06 -0700, Duncan wrote:
>> From an outside perspective, I'm sure it's amazing and crass that USians
>> see nothing unusual about the national holiday of thanks being directly
>> followed by the biggest day of commercial greed in the entire year, as
>> the opening day of the biggest season of commercial greed, obsensibly as
>> preparation for the day of celebration of the birth of Jesus Christ, the
>> man seen as the Son of God, and quoted as saying it's easier for a camel
>> to pass thru the eye of a needle than for a rich man to get into
>> paradise! Interesting commentary on our culture!
>
> What the hell does this have to do with Gentoo development?
About the same as the original reference to "after the Thanksgiving
holiday" which prompted the question to which it is a reply, which was in
the context you snipped. As such, certainly as much or more than
oblique references to harems and goats and people's butts (well, unless
there's something about Gentoo development I don't know about, yet <g>),
all topics that have come up in passing on the list, just as this
did, without this question being asked of those posters.
It may be possible to automate code creation, but it's not possible to
automate a community, and humans in such a community /don't/ tend to stay
strictly on topic. That's just the way humans are, and have been for far
longer than either you or I have been around.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-23 21:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 18:15 [gentoo-dev] enewuser/enewgroup getting their own eclass Chris Gianelloni
2005-11-23 18:30 ` Diego 'Flameeyes' Pettenò
2005-11-23 19:22 ` Chris Gianelloni
2005-11-23 20:06 ` [gentoo-dev] " Duncan
2005-11-23 20:21 ` Robin H. Johnson
2005-11-23 20:29 ` Chris Gianelloni
2005-11-23 21:14 ` Duncan [this message]
2005-11-23 21:28 ` [gentoo-dev] " Ciaran McCreesh
2005-11-23 21:29 ` Ned Ludd
2005-11-23 22:02 ` Jakub Moc
2005-11-23 18:52 ` [gentoo-dev] " Brian Harring
2005-11-23 19:31 ` Chris Gianelloni
2005-11-23 19:40 ` Donnie Berkholz
2005-11-23 19:54 ` Chris Gianelloni
2005-11-23 20:38 ` Donnie Berkholz
2005-11-23 22:54 ` Henrik Brix Andersen
2005-11-23 21:03 ` Donnie Berkholz
2005-11-23 23:17 ` Henrik Brix Andersen
2005-11-24 3:44 ` Mike Frysinger
2005-11-24 13:54 ` Chris Gianelloni
2005-11-24 19:34 ` Mike Frysinger
2005-11-25 14:24 ` Chris Gianelloni
2005-11-25 19:24 ` Mike Frysinger
2005-11-30 14:51 ` Chris Gianelloni
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=pan.2005.11.23.21.14.30.586966@cox.net \
--to=1i5t5.duncan@cox.net \
--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