Timeline for How to handle updated configuration when it's already been cloned for editing
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2014 at 13:53 | comment | added | alexrussell | @ both - yeah while writing up a clarification of my situation I realised that the problem is the way the configuration cascading works (or doesn't work, I should say). And while I could edit the 'published' configuration file, I'm not really supposed to in the spirit of the system I am working in. So yeah, I think I need to take the issue up with upstream. | |
| Jun 11, 2014 at 13:06 | comment | added | Doc Brown | +1, exactly my thoughts. I did not understand as well why the OP excludes the possibility of adding the missing keys automatically. There is no need to have an automatic installation or update process for that, the only thing one needs is write access to the user config at the time the software is started. | |
| Jun 11, 2014 at 12:58 | history | answered | Fil | CC BY-SA 3.0 |