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/osmo-bts/+/20826 ) Change subject: oml: Set NM_OPSTATE_DISABLED by default ...................................................................... Patch Set 1: I always found it rather nice to see those kind of state change reports when the TCP connection comes up. After all, the fact that we terminate osmo-bts (and hence reset all state) on loss of the TCP connection is an implementation detail, and not one that I'm particularly proud of. So imagine osmo-bts running across TCP reconnects. Then it would of course be great to get information about the current state of all objects at the time you reconnect. -- To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/20826 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-bts Gerrit-Branch: master Gerrit-Change-Id: I5ba6756ea069d0f995f453ee4b27e6839c914eb1 Gerrit-Change-Number: 20826 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-CC: laforge <laforge at osmocom.org> Gerrit-Comment-Date: Wed, 21 Oct 2020 17:08:01 +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/20201021/74c73d4c/attachment.htm>