This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
Harald Welte gerrit-no-reply at lists.osmocom.orgPatch Set 1: > I would gladly separate the hex category out to its own logging > config api, the only reason why I'm continuing to tie it with the > filename is backwards compat. If you agree that we completely untie > it from the filename (and that changing the logging API behavior is > acceptable) I'll change the patches. I'm not sure why we would change the behavoir? If we just add a new function which can disable the printing of th ehex category prefix, and make sure that the start-up default is "enabled", how are we breaking compatibility? -- To view, visit https://gerrit.osmocom.org/5812 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Iba03a2b7915853c6dccaf6c393c31405320538b4 Gerrit-PatchSet: 1 Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Owner: Neels Hofmeyr <nhofmeyr at sysmocom.de> Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: Neels Hofmeyr <nhofmeyr at sysmocom.de> Gerrit-HasComments: No