Wim Taymans e088dd2d2f journal: copy log level to chained logger ... Make sure the log level on the chained logger is the same as ours. Makes PIPEWIRE_DEBUG=3 make run print debug again. This used to work because the log level was parsed and set before the loggers were created and chained, and so they all got the same level. Now that the level can be changed with metadata at runtime, we can't really update all past loggers so let the journal logger copy the level itself.		2024-01-04 13:57:26 +01:00
..
aec	spa: export log topic enumerations	2024-01-04 10:02:55 +00:00
alsa	spa: export log topic enumerations	2024-01-04 10:02:55 +00:00
audioconvert	spa: export log topic enumerations	2024-01-04 10:02:55 +00:00
audiomixer	spa: export log topic enumerations	2024-01-04 10:02:55 +00:00
audiotestsrc
avb	spa: export log topic enumerations	2024-01-04 10:02:55 +00:00
bluez5	spa: use only static log topics	2024-01-04 10:02:55 +00:00
control
ffmpeg
jack
libcamera	spa: export log topic enumerations	2024-01-04 10:02:55 +00:00
support	journal: copy log level to chained logger	2024-01-04 13:57:26 +01:00
test
v4l2	spa: export log topic enumerations	2024-01-04 10:02:55 +00:00
videoconvert	spa: export log topic enumerations	2024-01-04 10:02:55 +00:00
videotestsrc
volume
vulkan
meson.build