Hi Joerg,
2009/2/19 Joerg Pulz
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> On Thu, 19 Feb 2009, Arnaud Quette wrote:
>
> Hi Volker,
>>
>> I forward your request to the user list since I don't currently have much
>> time to process it.
>> quickly testing 2.4.1, I wasn't able to repro
Citeren Volker Theile :
> Ahmmm, just wondering how this could happen and why nobody has realized
> this bug during the testing phase :-)
Testing can only confirm the presence of bugs, not the absence. This
error was already present since (at least) January 2005, which
probably means that you
Aaaarrr seems i was blind yesterday night. I compared this file
with 2.2.2, registered some changes but did not check them :-( Anyway
thanks for the patch.
Regards
Volker
Joerg Pulz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> On Thu, 19 Feb 2009, Arnaud Quette wrote:
Ahmmm, just wondering how this could happen and why nobody has realized
this bug during the testing phase :-)
Joerg Pulz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> On Thu, 19 Feb 2009, Arnaud Quette wrote:
>
>> Hi Volker,
>>
>> I forward your request to the user list since I d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 19 Feb 2009, Arnaud Quette wrote:
Hi Volker,
I forward your request to the user list since I don't currently have much
time to process it.
quickly testing 2.4.1, I wasn't able to reproduce it.
a question: was it working with the exact sam
Hi Volker,
I forward your request to the user list since I don't currently have much
time to process it.
quickly testing 2.4.1, I wasn't able to reproduce it.
a question: was it working with the exact same context/config with 2.2.2?
cheers,
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://www
6 matches
Mail list logo
