On Mon, 8 Aug 2011 16:31:40 +0200, sean finney wrote:
On Mon,
Aug 08, 2011 at 01:58:27PM +0100, Ian Jackson wrote:
Keith Lawson
writes (How to close bug #620550?): 2. Unless someone knows why PHP is
using qdbm, it should IMO be switched back to gdbm. This is not RC I
think.
I refer
Keith Lawson writes (How to close bug #620550?):
I'm looking for advice on how to get bug #620550[1] closed. This
thread[2] on php-maint is the only record I can find of why PHP was
switched from GDBM to QDBM. That change introduced gdbm_ symbol
conflicts that end up breaking GDBM
hi,
I'm sorry that I've stopped its progress.
On Mon, Aug 8, 2011 at 9:58 PM, Ian Jackson
ijack...@chiark.greenend.org.uk wrote:
Keith Lawson writes (How to close bug #620550?):
I'm looking for advice on how to get bug #620550[1] closed. This
thread[2] on php-maint is the only record I can
On Mon, Aug 08, 2011 at 01:58:27PM +0100, Ian Jackson wrote:
Keith Lawson writes (How to close bug #620550?):
2. Unless someone knows why PHP is using qdbm, it should IMO be
switched back to gdbm. This is not RC I think.
I refer you, good sir, to the fine changelog for reference
sean finney writes (Re: How to close bug #620550?):
On Mon, Aug 08, 2011 at 01:58:27PM +0100, Ian Jackson wrote:
Keith Lawson writes (How to close bug #620550?):
2. Unless someone knows why PHP is using qdbm, it should IMO be
switched back to gdbm. This is not RC I think.
I refer
]] Ian Jackson
| sean finney writes (Re: How to close bug #620550?):
| On Mon, Aug 08, 2011 at 01:58:27PM +0100, Ian Jackson wrote:
| Keith Lawson writes (How to close bug #620550?):
| 2. Unless someone knows why PHP is using qdbm, it should IMO be
|switched back to gdbm
Hello,
I'm looking for advice on how to get bug #620550[1] closed. This
thread[2] on php-maint is the only record I can find of why PHP was
switched from GDBM to QDBM. That change introduced gdbm_ symbol
conflicts that end up breaking GDBM functionality in other packages
(mod_perl2 in my
7 matches
Mail list logo
