Update patch set 2

Patch Set 2:

(1 comment)

Patch-set: 2
Attention: {"person_ident":"Gerrit User 1000004 \u003c1000004@035e6965-6537-41bd-912c-053f3cf69326\u003e","operation":"ADD","reason":"\u003cGERRIT_ACCOUNT_1000010\u003e replied on the change"}
Attention: {"person_ident":"Gerrit User 1000010 \u003c1000010@035e6965-6537-41bd-912c-053f3cf69326\u003e","operation":"REMOVE","reason":"\u003cGERRIT_ACCOUNT_1000010\u003e replied on the change"}
This commit is contained in:
Gerrit User 1000010 2024-02-16 19:39:33 +00:00 committed by Gerrit Code Review
parent 5d2ca9f10b
commit 9ff12065dd
1 changed files with 24 additions and 0 deletions

View File

@ -22,6 +22,30 @@
},
"revId": "5862edb2d338446b0e06d14a0beafeb956f8c070",
"serverId": "035e6965-6537-41bd-912c-053f3cf69326"
},
{
"unresolved": true,
"key": {
"uuid": "cb5bed10_015aa14c",
"filename": "tests/vty/ss7_asp_test.vty",
"patchSetId": 2
},
"lineNbr": 426,
"author": {
"id": 1000010
},
"writtenOn": "2024-02-16T19:39:33Z",
"side": 1,
"message": "In general, the same problem can occur even if we keep the old commands unchanged: we oftentimes add new commands / VTY nodes and some of them show up in the output of `show running-config` or `write file ...`. This also breaks compatibility, but why would you want to [re-]generate configs for old software using new software in the first place...",
"parentUuid": "1aaab25f_0ac3392f",
"range": {
"startLine": 425,
"startChar": 0,
"endLine": 426,
"endChar": 20
},
"revId": "5862edb2d338446b0e06d14a0beafeb956f8c070",
"serverId": "035e6965-6537-41bd-912c-053f3cf69326"
}
]
}