public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Todd Berman <tberman@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Announcing a new developer (belatedly)
Date: 30 Jul 2003 19:26:16 -0400	[thread overview]
Message-ID: <1059607536.7882.12.camel@proton.sevenl.net> (raw)

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

As many of you might have noticed, the issue of develop announcements
has come up. I was somewhat lax in announcing my quasi-padawan Aether
(Jason Mobarak).

I say quasi because a potential dev-java developer was stolen right out
from under my nose by evil evil Seemant Kulleen and Aether's distinct
love of python. And I will never admit his distaste for Java factored
into it in the least, because, it didn't.

However, before he was ripped from the wonders that is Java development,
Aether managed to put together a brand spanking new java-config ( in
python though *grr* ). It solves many issues with the old sh
java-config, and it allows easy expansion of java-config. In fact, the
core could potentially be used as a base for all the -config tools
(distcc, gcc, etc) as it seems very extensible.

Aether also hails from our very own Daniel Robbins' home town.  He is a
second year CS student at UNM. And according to him he enjoys long walks
in the moonlight, and candle-lit dinner.

As I type this Seemant (evil, hss, boo, etc) is most likely typing out
an introduction that pretends he never stole Aether, or some other such
nonsense. I suggest you ignore his email, as it is most likely full of
half-truths and other such things.

--Todd

PS - DISCLAIMER, ETC : This is a joke, just in case anyone missed it,
except for what Aether did.   Oh, and the parts about Seemant ;P

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2003-07-30 23:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1059607536.7882.12.camel@proton.sevenl.net \
    --to=tberman@gentoo.org \
    --cc=gentoo-dev@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