Message264682
Having both `defaults` and `overrides` would confuse the API, especially given that we already have `fallback` arguments to `get*` methods.
What's the point of having overrides *over* a file? Defaults were thought of as a way to say: "unless the user bothered to modify those, the values are as follows". That's the point of configuration. We have defaults, that the *user* overrides. Why would you want to override what the user specified? I fail to understand the logic behind this. |
|
Date |
User |
Action |
Args |
2016-05-02 23:19:40 | lukasz.langa | set | recipients:
+ lukasz.langa, SilentGhost, Marc.Abramowitz |
2016-05-02 23:19:40 | lukasz.langa | set | messageid: <1462231180.93.0.483662927199.issue26710@psf.upfronthosting.co.za> |
2016-05-02 23:19:40 | lukasz.langa | link | issue26710 messages |
2016-05-02 23:19:40 | lukasz.langa | create | |
|