Message-Id: <email address hidden>
Date: Tue, 03 Aug 2004 09:40:23 +0100
From: Crispin Flowerday <email address hidden>
To: <email address hidden>
Subject: bug 261452, definately a mozilla bug
reassign 261452 mozilla-browser
thanks
I hope I'm not stepping on anyone's toes by pushing this myself to
mozilla, but I have had confirmation from the mozilla developers that
the patch for bug 246675 is the cause of the problem:
crispin | can anyone confirm whether the fix for bug 246675 caused bug 251648 ?
biesi | crispin, correct, it did
crispin | biesi: thanks for confirming that, debian has applied the patch for 246675, so cookies are horribly broken :-(
biesi | oh. heh. they absolutely need that second one.
(the bug numbers in the irc extract are for the bugzilla.m.o bug database)
(this also needs to be merged with bug 262468, but I don't know how to
do that :-) )
Message-Id: <email address hidden>
Date: Tue, 03 Aug 2004 09:40:23 +0100
From: Crispin Flowerday <email address hidden>
To: <email address hidden>
Subject: bug 261452, definately a mozilla bug
reassign 261452 mozilla-browser
thanks
I hope I'm not stepping on anyone's toes by pushing this myself to
mozilla, but I have had confirmation from the mozilla developers that
the patch for bug 246675 is the cause of the problem:
crispin | can anyone confirm whether the fix for bug 246675 caused bug 251648 ?
biesi | crispin, correct, it did
crispin | biesi: thanks for confirming that, debian has applied the patch for 246675, so cookies are horribly broken :-(
biesi | oh. heh. they absolutely need that second one.
(the bug numbers in the irc extract are for the bugzilla.m.o bug database)
(this also needs to be merged with bug 262468, but I don't know how to
do that :-) )
Crispin