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/.
laforge gerrit-no-reply at lists.osmocom.orglaforge has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/19463 ) Change subject: log stderr: Increase output buffering using setvbuf() ...................................................................... Patch Set 2: (1 comment) https://gerrit.osmocom.org/c/libosmocore/+/19463/1//COMMIT_MSG Commit Message: https://gerrit.osmocom.org/c/libosmocore/+/19463/1//COMMIT_MSG@7 PS1, Line 7: log stderr: Increase output buffering using setvbuf() > The changes you are doing here doesn't seem to correspond to log stderr, but to file targets. […] thanks, indeed. for stderr I'm not sure setvbuf can be used. It must be used immediately after opening the file descriptor... 128 is just a random number, which I felt was sufficiently large as a buffer. But we could of course make that also user/application configurable -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/19463 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: I59beadb8d1d10a942513efc4c0477701f967237a Gerrit-Change-Number: 19463 Gerrit-PatchSet: 2 Gerrit-Owner: laforge <laforge at osmocom.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge at osmocom.org> Gerrit-CC: pespin <pespin at sysmocom.de> Gerrit-Comment-Date: Tue, 04 Aug 2020 14:31:06 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: pespin <pespin at sysmocom.de> Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20200804/f13c7b66/attachment.htm>