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/.
pespin gerrit-no-reply at lists.osmocom.orgpespin has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/20575 ) Change subject: vty: Set TCP_NODELAY on VTY sockets ...................................................................... Patch Set 1: That brings us back to the discussion on what is more important regarding logging: delaying logging to safe some resources or to receive the logging content as soon as possible. I get your point too regarding logging. We could enable/disable NODELAY dynamically based on whether logging is enabled or not, that would be an option. -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/20575 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: I34f8d3ac70045e48613f67e3c79c2ff49c4d2794 Gerrit-Change-Number: 20575 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge at osmocom.org> Gerrit-Comment-Date: Mon, 12 Oct 2020 15:15:37 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: No Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20201012/6058f138/attachment.htm>