Re: Allow rb to use any io_device/registered name instead of only filename path

Fredrik <[email protected]>
Newsgroups gmane.comp.lang.erlang.patches
Message-ID <[email protected]>
On 06/04/2013 11:59 PM, PAILLEAU Eric wrote:
> Le 04/06/2013 09:13, Fredrik a écrit :
>> On 06/02/2013 12:06 PM, PAILLEAU Eric wrote:
>>> Hello,
>>> Report Browser could not accept a file descriptor,
>>> for instance given by another application.
>>> this is a first patch needed in my wish to
>>> add a graphical log browser in observer.
>>>
>>> git fetch https://github.com/crownedgrouse/otp.git add_fd_usage_in_rb
>>>
>>> https://github.com/crownedgrouse/otp/compare/erlang:maint...add_fd_usage_in_rb
>>>
>>>
>>> https://github.com/crownedgrouse/otp/compare/erlang:maint...add_fd_usage_in_rb.patch
>>>
>>>
>>> regards
>>>
>>> _______________________________________________
>>> erlang-patches mailing list
>>> [email protected]
>>> http://erlang.org/mailman/listinfo/erlang-patches
>> Hello Eric,
>> Your patch is failing the following testcases:
>> Application: SASL, Suite: rb_SUITE, Testcase: list;
>> Application: SASL, Suite: rb_SUITE, Testcase: rescan
>>
> Hello,
> please refetch.
> I came back to former behaviour for rb:list/1-2 functions, so the test
> suite do not fail anymore.
> I add 2 new exported function that allow to print list of reports in the
> log file.
> Regards
> _______________________________________________
> erlang-patches mailing list
> [email protected]
> http://erlang.org/mailman/listinfo/erlang-patches
Hello Eric,
We just stumbled across in your patch that you have merged maint into 
your patch,
which you not should do. Do a rebase upon the latest maint branch on our 
github instead and notify us when done.
Thanks,

-- 

BR Fredrik Gustafsson
Erlang OTP Team

_______________________________________________
erlang-patches mailing list
[email protected]
http://erlang.org/mailman/listinfo/erlang-patches
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.