From: Tal Peer <coredumb@gentoo.org>
To: FRLinux <frlinux@frlinux.net>
Cc: gentoo-dev ML <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] PHP5 stuff..
Date: Mon, 14 Jul 2003 12:23:20 +0300 (IDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0307141222070.6239@err> (raw)
In-Reply-To: <1058171323.4101.8.camel@localhost>
On Mon, 14 Jul 2003, FRLinux wrote:
> > 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 ?
After discussing that with a few other devs, i've decided that php-cvs
stays (and see my next mail for more cvs related stuff).
Tal
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-14 9:23 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
2003-07-14 9:23 ` Tal Peer [this message]
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=Pine.LNX.4.53.0307141222070.6239@err \
--to=coredumb@gentoo.org \
--cc=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