3 | | @cjones051073 I expect to have to maintain my changes across updates, but I can't do that, when everything is lost. Additionaly, most software does not require changes to configuration files on every update. Git does not. Compiled-in default rarely change, and git happily accepts even the most ancient of configurations. It just reads what it understands and ignores any settings that might have been removed. The vast majority of users would also not have problems if everything unchanged is updated properly, while for those who do changes, replacing the file definitely DOES break things. Suddenly I accidently commit files to my repos that should be ignored (like "Icon\r"), aliases stop working, and unicode filenames get decomposed. Closing bugs as "wontfix" is just another way of saying: "I don't care and I'm too lazy to work on it." |
| 3 | @cjones051073 I expect to have to maintain my changes across updates, but I can't do that, when everything is lost. Additionaly, most software does not require changes to configuration files on every update. Git does not. Compiled-in defaults rarely change, and git happily accepts even the most ancient of configurations. It just reads what it understands and ignores any settings that might have been removed. The vast majority of users would also not have problems if everything unchanged is updated properly, while for those who do changes, replacing the file definitely DOES break things. Suddenly I accidently commit files to my repos that should be ignored (like "Icon\r"), aliases stop working, and unicode filenames get decomposed. Closing bugs as "wontfix" is just another way of saying: "I don't care and I'm too lazy to work on it." |