On 10/20/2015 1:52 PM, Anil Madhavapeddy wrote:
>
>> On 7 Oct 2015, at 18:25, Paul Skentzos wrote:
>>
>> Anil,
>>
>> On 10/7/2015 12:36 PM, Anil Madhavapeddy wrote:
>>> On 7 Oct 2015, at 15:53, Paul Skentzos
>>> wrote:
Hi Luke,
On 10/7/2015 10:15 AM, Luke Dunstan wrote:
>>
Le vendredi, 23 octobre 2015 à 13:49, Drup a écrit :
> However I have trouble understand what is the intended use case for
> tags, and in particular why they are parametrized.
Maybe it's over engineering at work; I never used that personally for now.
There are two intended use cases:
1) If lib
I globally like the API (it's similar to Lwt_log, which I already quite
liked).
However I have trouble understand what is the intended use case for
tags, and in particular why they are parametrized. It doesn't seem to be
possible to filter by tag in a programmatic way.
Le 23/10/2015 03:18, D
Begin forwarded message:
> From: Jakub Jermar
> Date: 23 October 2015 at 05:17:03 GMT-7
> To: HelenOS development mailing list ,
> genode-m...@lists.sourceforge.net, bug-h...@gnu.org, Julian Stecklina
> , Björn Döbel ,
> sarta...@ksyslabs.org, rumpkernel-us...@freelists.org, devel@sel4.syst
Thanks for taking time to feedback, always appreciated !
Le vendredi, 23 octobre 2015 à 09:49, Thomas Leonard a écrit :
> Having a default level for new sources seems a bit ugly. If I
> understand correctly, this is a global that can only be used correctly
> if you know when your libraries are g
On 23 October 2015 at 02:18, Daniel Bünzli wrote:
> Ok so here's something:
>
> http://erratique.ch/software/logs
> http://erratique.ch/software/logs/doc/
>
> Given that it's clearly superior from a disabled logging performance point of
> view, Logs uses Dr. Yallop's formatting continuation t
