bsite -- so don't
be alarmed! :)
-- james
--
James Cox :: james at imajes dot info :: http://imajes.info/
Was I helpful?
http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/
Frederick: That's your guy, you've just escaped from an intergalactic,
maximum security prison po
>
> The problem isn't the ending. The problem is that according
> to our naming conventions it should be array_foobar() whereas the
other
> array functions were invented before our conventions and are short
names such
> as next(). Now on one hand we wouldn't want to pollute the PHP
function
>
>
> Since there's been a lot of talk about disabling mysql by
> default (and
> having another option available), the PostgreSQL people are
> pretty excited
> about this and are keen to see what can be done about getting
> postgres
> enabled by default instead.
>
I certainly don't speak fo
And so on.
Once you guys realize how that php4 can't be in the same tree as php5,
then you will begin to realize what it was that I was trying to do.
> -Original Message-
> From: admin [mailto:admin] On Behalf Of Sebastian Bergmann
> Sent: Tuesday, June 24, 2003 6:20 AM
> To: [EMAIL PROT
>
> At 10:32 AM 6/23/2003 -0700, Rasmus Lerdorf wrote:
> >A bunch of things are broken. Files are missing in php4
> head and the
> >wrong versions of files are also in there. I think we need to roll
> >this change back as soon as possible and take another shot
> at this in a
> >much more or
>
> I am not quite sure how/what broke. However, no matter if
> what James did was the right or wrong thing to do, I think it should
have
> been discussed first (in detail).
>
The opportunity was made available, many times.
-- james
--
PHP Internals - PHP Runtime Development Mailing Li
>
> There is one fix for all of this, the most appropriate fix,
> which is to properly revert a file to revisions previous to
> the first php5 development, and then bring HEAD into sync
> with the branch [1].
>
The reference here was
http://elib.cs.berkeley.edu/admin/cvs/cvsrevert.html ... S
>
> The problem is that I now have conflicts in my changes
> because CVS was doing its job and merging changes into my
> local code. In addition, some of my changes have been
> clevery merged with 4.3 specific changes. So, I have to go
> and audit my code by hand and check which of the change
> Can someone explain why James just made it impossible to
> properly work with source code which resides in PHP 4 and 5?
>
> - diffing is impossible
> - merging is impossible
> - history of new commits becomes fragmented
>
> James, why did not you discuss this first? All
>
> The point is that there are now a number of core developers
> who updated their existing php5 checkouts and now have a load
> of crap from 4.3 merged into their php5 development.
>
For what it's worth, the last 5 or so warning emails I have dropped onto
the list making it very clear what th
rate avail entry.
The next stage to happen is that I will bring php4 HEAD into sync with
the 4.x development branch, so expect a big patch.
-- james
--
James Cox :: [EMAIL PROTECTED] :: http://imajes.info/
Was I helpful?
http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO/
Alien: I brin
> Does it then make sense to have messages like this,
> "Subject: [PHP-CVS] cvs: php4 /ext/imap php_imap.c" from
> CVS?? or see all things of cvs related to php4.
>
I'm in the middle of 'fixing' this.
-- james
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: ht
> Wouldn't it be better to give [Zak] and MySQL AB a
> little bit more time?
I think this is the most sensible idea posted so far. The notion that we
*don't* lose out if we unbundle by default is wrong -- we're going to
have so many "my MySQL is broken, HELP!!!" support requests, it's going
to b
> On Mon Jun 09, 2003 at 03:1630PM +0100, James Cox wrote:
> > By moving PECL into the limelight. This week, I will be
> > splitting PECL into it's own cvs module, and (after discussion) I'd like
> > to create a version of pearweb for pecl.php.net, essentially se
work without all the minor problems
right now (eg, secure binaries, win32 support, etc etc). Then once we are
all using that instead of recompiles every time.. (which won't take long)
moving to PECL becomes a natural progression.
-- james
--
James Cox :: [EMAIL PROTECTED] :: http://imajes.i
>
> Is PECL going to move to the top level in CVS? - it's a bit
> hidden away
> at the moment... (and I guess after these are moved -
> creating a 'real'
> php5 directory?? - so their's not so many empty directories
> lying around?)
>
>
Yes. There are a bunch of cvs admin tasks that I am l
>
> So now that the PEAR framework for bundling extensions is in
> place, I figured I'd start a thread about moving all
> extensions to PECL, and then selectively bundling them from
> PECL (perhaps maintaining physical aliases as well.)
>
I'm +1 on this.. And already offered to move stuff, s
Guys,
you might have noticed that right now you are going to be recieving a flood
of mail to your php.net address. This is because we had a little issue on
our MX box that caused mail to queue rather than send.
Thanks,
-- james
--
James Cox :: [EMAIL PROTECTED] :: http://imajes.info/
Was I
Everything should be good now.
-- james
> -Original Message-
> From: Sascha Schumann [mailto:[EMAIL PROTECTED]
> Sent: 24 March 2003 19:25
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: [PHP-DEV] cvs commits disabled for now
>
>
> There are on-going proble
bonsai to return them to
service.
Thanks,
James Cox
>
> Just a heads up,
>
> we should be moving the cvs apparatus from one server to another
> in the next
> few hours. The only down time will be whilst your dns updates,
> and this will
> _only_ affect cvs COMMITS -- n
Just a heads up,
we should be moving the cvs apparatus from one server to another in the next
few hours. The only down time will be whilst your dns updates, and this will
_only_ affect cvs COMMITS -- not checkouts.
Thanks for your patience.
James Cox
php sysadmin
--
James Cox :: [EMAIL
Guys,
I have setup a new list for qa reports, ([EMAIL PROTECTED]) so that
qa discussion can continue on [EMAIL PROTECTED], and be more readable.
-- james
--
James Cox :: [EMAIL PROTECTED] :: http://imajes.info/
Was I helpful? http://www.amazon.co.uk/exec/obidos/wishlist/23IVGHQ61RJGO
>
> On Thu, 13 Mar 2003, James Cox wrote:
>
> > I asked joe to ask for commit privs as he's the redhat guy
> doing PHP work,
> > and has useful stuff to commit.
>
> I think that we can handle the 20 line patch manually for now.
>
Joe says he sent
I asked joe to ask for commit privs as he's the redhat guy doing PHP work,
and has useful stuff to commit.
-- james
> -Original Message-
> From: Joe Orton [mailto:[EMAIL PROTECTED]
> Sent: 13 March 2003 15:17
> To: [EMAIL PROTECTED]
> Subject: [PHP-DEV] CVS Account Request: jorton
>
>
>
Andrey, (and everyone else)
You are all subscribed to the new list -- forgot to mention.
Thanks,
James
> -Original Message-
> From: Andrey Hristov [mailto:[EMAIL PROTECTED]
> Sent: 13 March 2003 09:10
> To: James Cox
> Subject: Re: [PHP-DEV] List Administrivia
>
OK,
so [EMAIL PROTECTED] is now active, with the old subscriber list from
php-dev. At the request from Derick the subject prefix will remain [PHP-DEV]
so that those who filter on it will still be able too (and anyhow, that
makes more sense then internals..)
There is also now a digest mode which p
OK,
so [EMAIL PROTECTED] is now active, with the old subscriber list from
php-dev. At the request from Derick the subject prefix will remain [PHP-DEV]
so that those who filter on it will still be able too (and anyhow, that
makes more sense then internals..)
There is also now a digest mode which p
27 matches
Mail list logo
