Attention is currently required from: fixeria, laforge, osmith.
Patch set 1:Code-Review +1
2 comments:
Patchset:
this makes the code a lot nicer.
File src/hlr_vty.c:
Patch Set #1, Line 300: vty_out(vty, " no subscriber-create-on-demand%s", VTY_NEWLINE);
the point IMHO is less what each of us feel at this point, but more "what is consistent with the exi […]
my perception is we have not much consistency in that regard.
Some values we deem important to print defaults for, others we omit.
(Also for some we use 'foo delete' and for others 'no foo'... etc)
Contrary to my favorite, it seems to me that later osmocom does tend towards omitting defaults, while earlier osmocom used to write defaults more.
When I see new software I find it very useful to have a config file with all the options listed explicitly; often all the defaults are listed, but commented out, that's nice. That would be my personal favorite, but that would also be a totally new first for osmocom.
It is less code complexity to just write everything.
Is create-on-demand a fringe feature that needs no visibility? Depends on the corporate vs communal POV...
I'm afraid this is an endless discussion topic, I'd just let fixeria make a choice and be fine with that.
To view, visit change 37779. To unsubscribe, or for help writing mail filters, visit settings.