- gerrit-log - lists.osmocom.org

[S] Change in osmo-ttcn3-hacks[master]: M3UA_Templates: Allow passing multiple Routing Context values

by pespin

pespin has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/40189?usp=email ) Change subject: M3UA_Templates: Allow passing multiple Routing Context values ...................................................................... M3UA_Templates: Allow passing multiple Routing Context values Change-Id: I117c63786d71aea683b554cf294fee0ceed665e0 --- M library/M3UA_Templates.ttcn 1 file changed, 22 insertions(+), 22 deletions(-) git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/89/40189/1 diff --git a/library/M3UA_Templates.ttcn b/library/M3UA_Templates.ttcn index 3667ca0..1422b80 100644 --- a/library/M3UA_Templates.ttcn +++ b/library/M3UA_Templates.ttcn @@ -274,7 +274,7 @@ } template (value) PDU_M3UA ts_M3UA_ASPAC(template (omit) M3UA_Traffic_Mode_Type tmt, - template (omit) OCT4 rctx) := { + template (omit) octetstring rctx) := { m3UA_ASPAC := { version := c_M3UA_VERSION, reserved := '00'O, @@ -288,7 +288,7 @@ } } template (present) PDU_M3UA tr_M3UA_ASPAC(template M3UA_Traffic_Mode_Type tmt, - template OCT4 rctx) := { + template octetstring rctx) := { m3UA_ASPAC := { version := c_M3UA_VERSION, reserved := '00'O, @@ -303,7 +303,7 @@ } template (value) PDU_M3UA ts_M3UA_ASPAC_ACK(template (omit) M3UA_Traffic_Mode_Type tmt, - template (omit) OCT4 rctx) := { + template (omit) octetstring rctx) := { m3UA_ASPAC_Ack := { version := c_M3UA_VERSION, reserved := '00'O, @@ -317,7 +317,7 @@ } } template (present) PDU_M3UA tr_M3UA_ASPAC_ACK(template M3UA_Traffic_Mode_Type tmt, - template OCT4 rctx) := { + template octetstring rctx) := { m3UA_ASPAC_Ack := { version := c_M3UA_VERSION, reserved := '00'O, @@ -331,7 +331,7 @@ } } -template (value) PDU_M3UA ts_M3UA_ASPIA(template (omit) OCT4 rctx) := { +template (value) PDU_M3UA ts_M3UA_ASPIA(template (omit) octetstring rctx) := { m3UA_ASPIA := { version := c_M3UA_VERSION, reserved := '00'O, @@ -343,7 +343,7 @@ } } } -template (present) PDU_M3UA tr_M3UA_ASPIA(template OCT4 rctx) := { +template (present) PDU_M3UA tr_M3UA_ASPIA(template octetstring rctx) := { m3UA_ASPIA := { version := c_M3UA_VERSION, reserved := '00'O, @@ -357,7 +357,7 @@ } -template (value) PDU_M3UA ts_M3UA_ASPIA_ACK(template (omit) OCT4 rctx) := { +template (value) PDU_M3UA ts_M3UA_ASPIA_ACK(template (omit) octetstring rctx) := { m3UA_ASPIA_Ack := { version := c_M3UA_VERSION, reserved := '00'O, @@ -369,7 +369,7 @@ } } } -template (present) PDU_M3UA tr_M3UA_ASPIA_ACK(template OCT4 rctx) := { +template (present) PDU_M3UA tr_M3UA_ASPIA_ACK(template octetstring rctx) := { m3UA_ASPIA_Ack := { version := c_M3UA_VERSION, reserved := '00'O, @@ -418,7 +418,7 @@ } template (value) PDU_M3UA ts_M3UA_DUNA(template (value) M3UA_Point_Codes affected_pcs, - template (omit) OCT4 rctx := omit) := { + template (omit) octetstring rctx := omit) := { m3UA_DUNA := { version := c_M3UA_VERSION, reserved := '00'O, @@ -433,7 +433,7 @@ } } template (present) PDU_M3UA tr_M3UA_DUNA(template (present) M3UA_Point_Codes affected_pcs := ?, - template OCT4 rctx := *):= { + template octetstring rctx := *):= { m3UA_DUNA := { version := c_M3UA_VERSION, reserved := '00'O, @@ -449,7 +449,7 @@ } template (value) PDU_M3UA ts_M3UA_DAVA(template (value) M3UA_Point_Codes affected_pcs, - template (omit) OCT4 rctx := omit) := { + template (omit) octetstring rctx := omit) := { m3UA_DAVA := { version := c_M3UA_VERSION, reserved := '00'O, @@ -464,7 +464,7 @@ } } template (present) PDU_M3UA tr_M3UA_DAVA(template (present) M3UA_Point_Codes affected_pcs := ?, - template OCT4 rctx := *):= { + template octetstring rctx := *):= { m3UA_DAVA := { version := c_M3UA_VERSION, reserved := '00'O, @@ -480,7 +480,7 @@ } template (value) PDU_M3UA ts_M3UA_DAUD(template (value) M3UA_Point_Codes affected_pcs, - template (omit) OCT4 rctx := omit) := { + template (omit) octetstring rctx := omit) := { m3UA_DAUD := { version := c_M3UA_VERSION, reserved := '00'O, @@ -495,7 +495,7 @@ } } template (present) PDU_M3UA tr_M3UA_DAUD(template (present) M3UA_Point_Codes affected_pcs := ?, - template OCT4 rctx := *):= { + template octetstring rctx := *):= { m3UA_DAUD := { version := c_M3UA_VERSION, reserved := '00'O, @@ -511,7 +511,7 @@ } template (value) PDU_M3UA ts_M3UA_SCON(template (value) M3UA_Point_Codes affected_pcs, - template (omit) OCT4 rctx := omit) := { + template (omit) octetstring rctx := omit) := { m3UA_SCON := { version := c_M3UA_VERSION, reserved := '00'O, @@ -528,7 +528,7 @@ } } template (present) PDU_M3UA tr_M3UA_SCON(template (present) M3UA_Point_Codes affected_pcs := ?, - template OCT4 rctx := *):= { + template octetstring rctx := *):= { m3UA_SCON := { version := c_M3UA_VERSION, reserved := '00'O, @@ -548,7 +548,7 @@ template (value) PDU_M3UA ts_M3UA_DUPU(template (value) M3UA_Point_Codes affected_pcs, template (value) OCT2 cause, template (value) OCT2 user, - template (omit) OCT4 rctx := omit) := { + template (omit) octetstring rctx := omit) := { m3UA_DUPU := { version := c_M3UA_VERSION, reserved := '00'O, @@ -566,7 +566,7 @@ template (present) PDU_M3UA tr_M3UA_DUPU(template (present) M3UA_Point_Codes affected_pcs := ?, template (present) OCT2 cause := ?, template (present) OCT2 user := ?, - template OCT4 rctx := *):= { + template octetstring rctx := *):= { m3UA_DUPU := { version := c_M3UA_VERSION, reserved := '00'O, @@ -628,7 +628,7 @@ template (value) PDU_M3UA ts_M3UA_ERR(template (value) OCT4 err_code, - template (omit) OCT4 rctx) := { + template (omit) octetstring rctx) := { m3UA_ERR := { version := c_M3UA_VERSION, reserved := '00'O, @@ -644,7 +644,7 @@ } } template (present) PDU_M3UA tr_M3UA_ERR(template (present) OCT4 err_code, - template OCT4 rctx) := { + template octetstring rctx) := { m3UA_ERR := { version := c_M3UA_VERSION, reserved := '00'O, @@ -663,7 +663,7 @@ template (value) PDU_M3UA ts_M3UA_NOTIFY(template (value) OCT2 status_type, template (value) OCT2 status_info, - template (omit) OCT4 rctx, + template (omit) octetstring rctx, template (omit) OCT4 aspid := omit, template (omit) octetstring infostr := omit) := { m3UA_NOTIFY := { @@ -681,7 +681,7 @@ } template (present) PDU_M3UA tr_M3UA_NOTIFY(template (present) OCT2 status_type, template (present) OCT2 status_info, - template OCT4 rctx, + template octetstring rctx, template OCT4 aspid := *, template octetstring infostr := *) := { m3UA_NOTIFY := { -- To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/40189?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: newchange Gerrit-Project: osmo-ttcn3-hacks Gerrit-Branch: master Gerrit-Change-Id: I117c63786d71aea683b554cf294fee0ceed665e0 Gerrit-Change-Number: 40189 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de>

2 months, 1 week

1
0
0 0

[S] Change in libosmocore[master]: vty: cosmetic: fix code formatting

by fixeria

fixeria has submitted this change. ( https://gerrit.osmocom.org/c/libosmocore/+/40186?usp=email ) Change subject: vty: cosmetic: fix code formatting ...................................................................... vty: cosmetic: fix code formatting Change-Id: I746b72dc79b6ebf2e3cb18274118f3ca9ead312a --- M src/vty/command.c 1 file changed, 6 insertions(+), 6 deletions(-) Approvals: pespin: Looks good to me, approved Jenkins Builder: Verified laforge: Looks good to me, but someone else must approve diff --git a/src/vty/command.c b/src/vty/command.c index 8f87e7d..8594290 100644 --- a/src/vty/command.c +++ b/src/vty/command.c @@ -3555,13 +3555,13 @@ config_write_cmd, "write", "Write running configuration to memory, network, or terminal\n") - ALIAS(config_write_file, +ALIAS(config_write_file, config_write_memory_cmd, "write memory", "Write running configuration to memory, network, or terminal\n" "Write configuration to the file (same as write file)\n") - ALIAS(config_write_file, +ALIAS(config_write_file, copy_runningconfig_startupconfig_cmd, "copy running-config startup-config", "Copy configuration\n" @@ -3569,7 +3569,7 @@ "Copy running config to startup config (same as write file)\n") /* Write current configuration into the terminal. */ - DEFUN(config_write_terminal, +DEFUN(config_write_terminal, config_write_terminal_cmd, "write terminal", "Write running configuration to memory, network, or terminal\n" @@ -3606,7 +3606,7 @@ "show running-config", SHOW_STR "running configuration\n") /* Write startup configuration into the terminal. */ - DEFUN(show_startup_config, +DEFUN(show_startup_config, show_startup_config_cmd, "show startup-config", SHOW_STR "Contentes of startup configuration\n") { @@ -3722,7 +3722,7 @@ "The UNENCRYPTED (cleartext) line password\n") /* VTY enable password set. */ - DEFUN(config_enable_password, enable_password_cmd, +DEFUN(config_enable_password, enable_password_cmd, "enable password (8|) WORD", "Modify enable password parameters\n" "Assign the privileged level password\n" @@ -3785,7 +3785,7 @@ "The UNENCRYPTED (cleartext) 'enable' password\n") /* VTY enable password delete. */ - DEFUN(no_config_enable_password, no_enable_password_cmd, +DEFUN(no_config_enable_password, no_enable_password_cmd, "no enable password", NO_STR "Modify enable password parameters\n" -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/40186?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: merged Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: I746b72dc79b6ebf2e3cb18274118f3ca9ead312a Gerrit-Change-Number: 40186 Gerrit-PatchSet: 1 Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>

2 months, 1 week

1
0
0 0

[XS] Change in libosmocore[master]: VTY: Initialize fields of struct cmd_element in order of declaration

by pespin

Attention is currently required from: jolly. pespin has posted comments on this change by jolly. ( https://gerrit.osmocom.org/c/libosmocore/+/40188?usp=email ) Change subject: VTY: Initialize fields of struct cmd_element in order of declaration ...................................................................... Patch Set 1: Code-Review+2 -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/40188?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: Ifaa31980f149f9c1f1a9b28f318a4850f6855472 Gerrit-Change-Number: 40188 Gerrit-PatchSet: 1 Gerrit-Owner: jolly <andreas(a)eversberg.eu> Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Attention: jolly <andreas(a)eversberg.eu> Gerrit-Comment-Date: Fri, 02 May 2025 11:16:47 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes

2 months, 1 week

1
0
0 0

[S] Change in libosmocore[master]: vty: cosmetic: fix code formatting

by pespin

Attention is currently required from: fixeria. pespin has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/libosmocore/+/40186?usp=email ) Change subject: vty: cosmetic: fix code formatting ...................................................................... Patch Set 1: Code-Review+2 -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/40186?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: I746b72dc79b6ebf2e3cb18274118f3ca9ead312a Gerrit-Change-Number: 40186 Gerrit-PatchSet: 1 Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Comment-Date: Fri, 02 May 2025 11:14:48 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes

2 months, 1 week

1
0
0 0

[XS] Change in libosmocore[master]: VTY: Initialize fields of struct cmd_element in order of declaration

by fixeria

Attention is currently required from: jolly. fixeria has posted comments on this change by jolly. ( https://gerrit.osmocom.org/c/libosmocore/+/40188?usp=email ) Change subject: VTY: Initialize fields of struct cmd_element in order of declaration ...................................................................... Patch Set 1: Code-Review+2 -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/40188?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: Ifaa31980f149f9c1f1a9b28f318a4850f6855472 Gerrit-Change-Number: 40188 Gerrit-PatchSet: 1 Gerrit-Owner: jolly <andreas(a)eversberg.eu> Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Attention: jolly <andreas(a)eversberg.eu> Gerrit-Comment-Date: Fri, 02 May 2025 08:55:23 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes

2 months, 1 week

1
0
0 0

[S] Change in libosmocore[master]: vty: remove broken 'show startup-config' command

by fixeria

Attention is currently required from: laforge. fixeria has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/libosmocore/+/40187?usp=email ) Change subject: vty: remove broken 'show startup-config' command ...................................................................... Patch Set 1: (2 comments) Commit Message: https://gerrit.osmocom.org/c/libosmocore/+/40187/comment/4bc1a658_0d812e58?… : PS1, Line 9: Saving the current configuration by doing 'write file [FILE]' breaks : the 'show startup-config' command. If write succeeds, this command : will be showing contents of the new (potentially modified) file. > e.g. https://blog.netwrix.com/copy-running-config-to-startup-config-cisco/ […] Ok, then I misunderstood the purpose of this command. My [incorrect] understanding was that this command is supposed to show the initial configuration that was effective when the process started. This might be useful, for instance, to see difference from the current (running) configuration. https://gerrit.osmocom.org/c/libosmocore/+/40187/comment/92a19250_c367c263?… : PS1, Line 12: If > Doesn't that mean that the write is then broken? In the ticket I gave an example of writing the configuration to *another* file, which is not the same as the one that the current process loaded. The problem occurs when you do `write file some_file`: `show startup-config` will be showing contents of that new `some_file` even if it's not the one that was given to the process via `-c` (and thus will not be used if you restart the process). Another problem occurs when you try writing to a location in which you don't have the write permissions: the `write file /forbidden/some_file` fails, but yet alters the VTY state, so `show startup-config` would be trying to `open()` that `/forbidden/some_file` and obviously would fail. Maybe we should change the `write file [PATH]` command to not alter the state, i.e. remove invocation of `host_config_set()` in `config_write_file_cmd`. This would solve both problems I described above. What do you think? -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/40187?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: If0b4a79052c060cad963e6458b29000a979f95ba Gerrit-Change-Number: 40187 Gerrit-PatchSet: 1 Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-CC: laforge <laforge(a)osmocom.org> Gerrit-Attention: laforge <laforge(a)osmocom.org> Gerrit-Comment-Date: Fri, 02 May 2025 08:53:03 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: laforge <laforge(a)osmocom.org>

2 months, 1 week

1
0
0 0

[XS] Change in libosmocore[master]: VTY: Initialize fields of struct cmd_element in order of declaration

by laforge

Attention is currently required from: jolly. laforge has posted comments on this change by jolly. ( https://gerrit.osmocom.org/c/libosmocore/+/40188?usp=email ) Change subject: VTY: Initialize fields of struct cmd_element in order of declaration ...................................................................... Patch Set 1: Code-Review+1 Verified+1 -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/40188?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: Ifaa31980f149f9c1f1a9b28f318a4850f6855472 Gerrit-Change-Number: 40188 Gerrit-PatchSet: 1 Gerrit-Owner: jolly <andreas(a)eversberg.eu> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Attention: jolly <andreas(a)eversberg.eu> Gerrit-Comment-Date: Fri, 02 May 2025 07:33:05 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes

2 months, 1 week

1
0
0 0

[S] Change in libosmocore[master]: vty: remove broken 'show startup-config' command

by laforge

Attention is currently required from: fixeria. laforge has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/libosmocore/+/40187?usp=email ) Change subject: vty: remove broken 'show startup-config' command ...................................................................... Patch Set 1: (1 comment) Commit Message: https://gerrit.osmocom.org/c/libosmocore/+/40187/comment/15abf817_13208d49?… : PS1, Line 9: Saving the current configuration by doing 'write file [FILE]' breaks : the 'show startup-config' command. If write succeeds, this command : will be showing contents of the new (potentially modified) file. e.g. https://blog.netwrix.com/copy-running-config-to-startup-config-cisco/ > show running-config — Displays the current active configuration of the device. > show startup-config — Shows the configuration _that will be loaded the next time the device restarts_. -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/40187?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: If0b4a79052c060cad963e6458b29000a979f95ba Gerrit-Change-Number: 40187 Gerrit-PatchSet: 1 Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-CC: laforge <laforge(a)osmocom.org> Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Comment-Date: Fri, 02 May 2025 07:32:18 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No Comment-In-Reply-To: laforge <laforge(a)osmocom.org>

2 months, 1 week

1
0
0 0

[S] Change in libosmocore[master]: vty: remove broken 'show startup-config' command

by laforge

Attention is currently required from: fixeria. laforge has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/libosmocore/+/40187?usp=email ) Change subject: vty: remove broken 'show startup-config' command ...................................................................... Patch Set 1: (2 comments) Commit Message: https://gerrit.osmocom.org/c/libosmocore/+/40187/comment/46cf8e4d_8390990f?… : PS1, Line 9: Saving the current configuration by doing 'write file [FILE]' breaks : the 'show startup-config' command. If write succeeds, this command : will be showing contents of the new (potentially modified) file. this is exactly how it would behave on a cisco device, isn't it? If you write to the file (basically `copy running-config startup-config`, then the [next] startup config is exactly the same as what you're running right now. I don't see a bug here. https://gerrit.osmocom.org/c/libosmocore/+/40187/comment/81449ac8_285ba68d?… : PS1, Line 12: If Doesn't that mean that the write is then broken? The write should probably always write to a newly-created file, and only after that succeeds unlink the old file and rename the new file, to ensure we always have either the old (unsuccesful write) or the new (successful write) config. If there is a related bug, it should be fixed in the write, and not worked around here? -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/40187?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: If0b4a79052c060cad963e6458b29000a979f95ba Gerrit-Change-Number: 40187 Gerrit-PatchSet: 1 Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-CC: laforge <laforge(a)osmocom.org> Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Comment-Date: Fri, 02 May 2025 07:29:00 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No

2 months, 1 week

1
0
0 0

[S] Change in libosmocore[master]: vty: cosmetic: fix code formatting

by laforge

Attention is currently required from: fixeria. laforge has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/libosmocore/+/40186?usp=email ) Change subject: vty: cosmetic: fix code formatting ...................................................................... Patch Set 1: Code-Review+1 -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/40186?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: I746b72dc79b6ebf2e3cb18274118f3ca9ead312a Gerrit-Change-Number: 40186 Gerrit-PatchSet: 1 Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Comment-Date: Fri, 02 May 2025 07:25:05 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes

2 months, 1 week

1
0
0 0

2025

2024

2023

2022

gerrit-log