cellular-infrastructure
/
osmo-msc
mirror of https://gerrit.osmocom.org/osmo-msc
9
0
Fork 0
Code Issues Releases Wiki Activity

Update patch set 1 

Patch Set 1:

(1 comment)

Patch-set: 1
Attention: {"person_ident":"Gerrit User 1000074 \u003c1000074@035e6965-6537-41bd-912c-053f3cf69326\u003e","operation":"REMOVE","reason":"\u003cGERRIT_ACCOUNT_1000074\u003e replied on the change"}
This commit is contained in:
Gerrit User 1000074 2024-03-26 14:24:56 +00:00 committed by Gerrit Code Review
parent 471cb5ee96
commit 5599cda878
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
3da4715f718dc8b695244ef4d9376f3724a9bb94
View File

@ -35,6 +35,24 @@
"revId": "3da4715f718dc8b695244ef4d9376f3724a9bb94",
"serverId": "035e6965-6537-41bd-912c-053f3cf69326"
},
{
"unresolved": false,
"key": {
"uuid": "d1718f8a_e55af610",
"filename": "/COMMIT_MSG",
"patchSetId": 1
},
"lineNbr": 15,
"author": {
"id": 1000074
},
"writtenOn": "2024-03-26T14:24:56Z",
"side": 1,
"message": "Yes, definetly drop the old one. In osmo-pcu is even more complex because we first lookup by TBF, and then the assigned MS object, but sometimes the MS object has non-yet-known-imsi. So at some point, when figuring out the IMSI, we figure out we have a duplicated MS object and we need to move gained information from the previous MS object and then drop that MS object plus its related TBFs.",
"parentUuid": "ee0aa82e_04e646a3",
"revId": "3da4715f718dc8b695244ef4d9376f3724a9bb94",
"serverId": "035e6965-6537-41bd-912c-053f3cf69326"
},
{
"unresolved": false,
"key": {