On Thu, 30.07.15 08:16, SF Markus Elfring (elfr...@users.sourceforge.net) wrote:
> >> Such messages correspond to specific data structures.
> >> * The log origin and log level are repeated there while the recorded
> >> information might occasionally not be detailed enough.
> >> I find that suc
>> I find that the change acceptance is unclear for fine-tuning of this software
>> also around message log programming interfaces.
>> Which design approaches do you find acceptable for further considerations?
>
> Sorry, I really can't follow.
How do you generally think about any further fine-tun
On Thu, Jul 30, 2015 at 8:16 AM, SF Markus Elfring
wrote:
>>> Such messages correspond to specific data structures.
>>> * The log origin and log level are repeated there while the recorded
>>> information might occasionally not be detailed enough.
>>> I find that such details can be better han
>> Such messages correspond to specific data structures.
>> * The log origin and log level are repeated there while the recorded
>> information might occasionally not be detailed enough.
>> I find that such details can be better handled by the software build
>> system.
…
> I appreciate you wan
Hi Markus,
On Wed, Jul 29, 2015 at 8:54 PM, SF Markus Elfring
wrote:
> Programs from the systemd software library output also some log messages
> as it is usual for such server applications.
>
> Such messages correspond to specific data structures.
> * The log origin and log level are repeated th
Hello,
Programs from the systemd software library output also some log messages
as it is usual for such server applications.
Such messages correspond to specific data structures.
* The log origin and log level are repeated there while the recorded
information might occasionally not be detailed