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-sgsn/+/15353 ) Change subject: Introduce FSM mm_state_gb_fsm ...................................................................... Patch Set 2: I beg to disagree. Why are we writign new code before we have any way of testing it in an automatic way? And not only writing the code, but actually submitting it for inclusion/merge? There's no problem if the test cases will mostly fail due to problems in the old code, and hopefully will gradually start to pass as more new code gets merged. But by not having the tests *before* a rewrite, you will never get around writing them. -- To view, visit https://gerrit.osmocom.org/c/osmo-sgsn/+/15353 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-sgsn Gerrit-Branch: master Gerrit-Change-Id: I04004423e993107374d5a3549b8a93ac169251dd Gerrit-Change-Number: 15353 Gerrit-PatchSet: 2 Gerrit-Owner: pespin <pespin at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: pespin <pespin at sysmocom.de> Gerrit-CC: laforge <laforge at gnumonks.org> Gerrit-Comment-Date: Mon, 02 Sep 2019 20:23:45 +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/20190902/a64a031f/attachment.htm>