> Well, for once, you can't use -A, which is quite annoying to begin
> with. In addition, various versions of CVS don't handle multiple sticky
> tags too well - so if you'd like to say, update to a certain date in the
> branch - it won't work (you can have just one sticky tag - either date or
> br
At 01:32 24/06/2003, Sascha Schumann wrote:
> I think that PHP 5 (or whatever the latest major version of PHP in the
> works is at a given moment) should be in HEAD, and not in a branch. CVS
> branches are really useful for maintaining old versions, but I think HEAD
> is the most suitable branch f
Sascha Schumann wrote:
> The great unification has commenced.
Thanks for your effort!
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
http://www.professionelle-softwareentwicklung-mit-php5.de/
--
PHP Internals - PHP Runtime Developm
Rob Richards wrote:
> Also, it looks like at least domxml and xslt were dropped from the
> php_4 branches.
There is, however, ext/sqlite in PHP_4_3 :)
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
http://www.professionelle-softwaree
On June 23, 2003 05:37 pm, Sascha Schumann wrote:
A clean checkout using "cvs co -r PHP_4_3 php-src-ze1" does not appear to
fetch the TSRM directory.
Ilia
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
"Sascha Schumann" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I haven't run into these.. details would certainly simplify
> that decision.
I found that it was not possible to get a diff between two dates with two -D
options in a branch which works fine in HEAD.
Edin
Just a couple of things about the current state of the repository.
A bunch of files in TSRM for PHP_5 need to be reverted to the previous
revision to get them back working with php5. The ones which were synched
with the php4 branch are now missing all the changes/fixes made to them over
the past x
> I think that PHP 5 (or whatever the latest major version of PHP in the
> works is at a given moment) should be in HEAD, and not in a branch. CVS
> branches are really useful for maintaining old versions, but I think HEAD
> is the most suitable branch for ongoing development(*), and we're not
> r
> Is it possible to perhaps make PHP_5 synonymous with HEAD while this is
> the main dev branch? Perhaps through an alias? The move the alias when
> the main dev branch becomes something else? It does seem a bit weird to
> not have main development on HEAD.
The lack of consistency regarding
At 00:37 24/06/2003, Sascha Schumann wrote:
The great unification has commenced.
There is now a single module php-src which contains all PHP 4
and PHP 5 branches.
BRANCH INFORMATION
Please make yourself familiar with the "cvs checkout -r
BRANCH" notation. It will be necessary
> PHP 5: cvs co -r PHP_5 php-src-ze2
Is it possible to perhaps make PHP_5 synonymous with HEAD while this is
the main dev branch? Perhaps through an alias? The move the alias when
the main dev branch becomes something else? It does seem a bit weird to
not have main development on HEA
On Mon, Jun 23, 2003 at 11:37:56PM +0200, Sascha Schumann wrote:
> The great unification has commenced.
>
> There is now a single module php-src which contains all PHP 4
> and PHP 5 branches.
>
> BRANCH INFORMATION
>
> Please make yourself familiar with the "cvs checkout -r
>
The great unification has commenced.
There is now a single module php-src which contains all PHP 4
and PHP 5 branches.
BRANCH INFORMATION
Please make yourself familiar with the "cvs checkout -r
BRANCH" notation. It will be necessary from now on for a
checkout.
Some
13 matches
Mail list logo
