Test (please ignore)
--
Mark Rotteveel
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
TEST
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Foo... Bar... Baz!
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 17-2-2019 18:36, liviuslivius wrote:
test message, because i have send two emails 16.02.2019 23:12
and 16.02.2019 23:27
but i still do see them on the group
I have them in my mailbox now, it looks like they were stuck for almost
a day within SourceForge:
Received: from [127.0.0.1]
test message, because i have send two emails 16.02.2019 23:12 and 16.02.2019
23:27
but i still do see them on the group
regards,
Karol Bieniaszewski
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
Test, please ignore
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
Test 2
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
test
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
Ignore please
Vlad
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
On 06/17/2016 07:11 PM, Dimitry Sibiryakov wrote:
> 17.06.2016 17:58, Dmitry Yemanov wrote:
>> Or perhaps do such a check in the remote client, or even better in the
>> Y-valve?
> In this case the test will fail always.
>
>
Tests are also fixed sometimes ;)
17.06.2016 17:58, Dmitry Yemanov wrote:
> Or perhaps do such a check in the remote client, or even better in the
> Y-valve?
In this case the test will fail always.
--
WBR, SD.
--
What NetFlow Analyzer can do for
17.06.2016 17:13, Dimitry Sibiryakov wrote:
>
> As most of you know, when routine protocol.cpp:alloc_cstring() receives zero
> length, it
> behaves differently, depending on previous allocations. In some cases it
> returns pointer
> to zero-length string, in some - NULL pointer.
> Because of
Hello, all.
As most of you know, when routine protocol.cpp:alloc_cstring() receives zero
length, it
behaves differently, depending on previous allocations. In some cases it
returns pointer
to zero-length string, in some - NULL pointer.
Because of this, used in subj test query
14 matches
Mail list logo