From: FRLinux <frlinux@frlinux.net>
To: gentoo-dev ML <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] PHP5 stuff..
Date: 14 Jul 2003 09:28:43 +0100 [thread overview]
Message-ID: <1058171323.4101.8.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.53.0307141117490.6239@err>
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
Hello, very good news that is, i'll do some test as soon as i can free
up my server at work.
> PS: If no one objects, I will remove php-cvs in the following days, as i
> see no reason for it being in the tree now that the PHP5 release cycle has
> begun.
What about further releases ? People might still want to use the CVS
release instead don't you think ?
Steph
--
Mail sent on Gentoo 1.4rc3 k2421 AMD 2600+
http://frlinux.net - frlinux@frlinux.net
http://gentoofr.org - Portail Francais sur Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-14 8:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 8:21 [gentoo-dev] PHP5 stuff Tal Peer
2003-07-14 8:28 ` FRLinux [this message]
2003-07-14 9:23 ` Tal Peer
2003-07-15 15:08 ` Markus Bertheau
2003-07-17 5:56 ` [gentoo-dev] " Sebastian Bergmann
2003-07-17 11:24 ` Tal Peer
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=1058171323.4101.8.camel@localhost \
--to=frlinux@frlinux.net \
--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