| 1 |
On Sun, 17 Jun 2018 19:35:05 -0700, Ian Zimmerman wrote: |
| 2 |
|
| 3 |
> The problem (or multiple problems) here is that it doesn't say what is |
| 4 |
> being merged into what (no, its not symmetric), and to compound that it |
| 5 |
> doesn't just leave this file alone and quit or go on to the next file; |
| 6 |
> it shows some diff again. What does this new diff mean? I can't make |
| 7 |
> sense of it without answering my other questions. |
| 8 |
> |
| 9 |
> To clarify: I don't think this is simply a usability problem that can be |
| 10 |
> addressed by using better or more verbose English. I think there is a |
| 11 |
> "big picture", a concept of what is being done, and this concept has not |
| 12 |
> found its way into the documentation or the UI itself. |
| 13 |
|
| 14 |
There are other config managers that handle this differently, if you |
| 15 |
don't like etc-update try another. I tried a few some years ago and |
| 16 |
settled on conf-update, others swear by cfg-update. conf-update lets you |
| 17 |
configure the diff and merge programs it uses but I stuck with the |
| 18 |
defaults except for using colordiff. Merging is interactive so you can |
| 19 |
choose whether you accept your old setting or the new default for each |
| 20 |
change. Like you, I treat my settings as the default and generally only |
| 21 |
merge in new additions to the config or changed defaults. |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Neil Bothwick |
| 26 |
|
| 27 |
Microbiology: staph only. |
Archives