public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stuart Herbert <stuart@gentoo.org>
To: gentoo-core@gentoo.org
Cc: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-core] New dev - stuart & turck-mmcache
Date: Sat, 19 Jul 2003 10:07:17 +0100	[thread overview]
Message-ID: <200307191007.21623.stuart@gentoo.org> (raw)
In-Reply-To: <20030719085050.GB32752@cherenkov.orbis-terrarum.net>

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 2052 bytes --]

Many thanks to Robin (robbat2), Seemant, Klieber, robh (or is it tigger now? 
lol ;-) and everyone else who's made me feel welcome during the last few 
weeks.

I've committed turck-mmcache 2.3.19 for testing.  This is a high-performance 
(and GPL'd ;-) PHP accelerator.  The original ebuild was submitted as bug 
#23360 by Klavs Klavsen.  Please take it out for a spin, and let me know how 
you get on.

If mmcache installs fine, but mysteriously doesn't work at all (no output in 
phpinfo(), /usr/share/turck-mmcache/mmcache.php says that it's not 
installed), please add a comment to bug #24792.

Best regards,
Stu
--
On Saturday 19 July 2003 9:50 am, Robin H.Johnson wrote:
> Now introducting a new developer...
> <Drumroll>
> Stuart Herbert (stuart@gentoo.org)
> </Drumroll>
>
> Stuart joins us after significent contributions to the Java
> functionality of PHP and other non-standard PHP extensions. He first
> started programming on Z80's around when I was born ;-).  He personally
> blames Alan Cox for getting him involved in Linux, and had a hand in
> testing the original TCP/IP stack for Linux with Alan. He has dabbled in
> writing a book or two, and currently does a bit of writing for the
> PHP|Architect.
>
> Stuart is also very interested in QA practices from his past employment,
> and has a lot of value insight to share on the subject. Esp on how to
> get QA done and make people not mind doing it ;-).
>
> Stuart has at least one other major linux contribution to his name...
> He wrote dialog-0.4, that added the radiolist control, and also came up
> with the puesdo-3D look after he was tired of it being flat 8-).

-- 
Stuart Herbert                                              stuart@gentoo.org
Gentoo Developer - PHP Bugs                            http://www.gentoo.org/
Upcoming packages list                http://dev.gentoo.org/~stuart/packages/

GnuGP key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319  C549 0C2F 80BA F9AF C57C
--

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

       reply	other threads:[~2003-07-19  9:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030719085050.GB32752@cherenkov.orbis-terrarum.net>
2003-07-19  9:07 ` Stuart Herbert [this message]
2003-07-20 12:39   ` [gentoo-dev] Re: [gentoo-core] New dev - stuart & turck-mmcache Dhruba Bandopadhyay
2003-07-20 12:14     ` Stuart Herbert
2003-07-20 12:23       ` Markus Bertheau
2003-07-20 13:20       ` Dhruba Bandopadhyay
2003-07-20 13:36         ` Stuart Herbert
2003-07-20 16:37           ` Dhruba Bandopadhyay
2003-07-22 10:09           ` Dhruba Bandopadhyay
2003-07-22  9:43             ` Stuart Herbert
2003-07-20 12:32 Mike Gardiner
2003-07-20 12:56 ` Paul de Vrieze

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=200307191007.21623.stuart@gentoo.org \
    --to=stuart@gentoo.org \
    --cc=gentoo-core@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