Noah Pendleton <noah.pendleton@xxxxxxxxx> writes: > Setting a global `blame.ignoreRevsFile` can be convenient, since I > usually use `.git-blame-ignore-revs` in repos. If the file is missing, > though, `git blame` exits with failure. This patch changes it to skip > over non-existent ignore-rev files instead of erroring. That cuts both ways, though. Failing upon missing configuration file is a way to catch misconfiguration that is hard to diagnose. I wonder if we can easily learn where the configuration variable came from in the codepath that diagnoses it as a misconfiguration. If it came from a per-repo configuration and names a non-existent file, it clearly is a misconfiguration that we want to flag as an error. Even if it came from a per-user configuration, if it was specified in a conditionally included file, it is likely to be a misconfiguration. If it came from a per-user configuration that applies without any condition, it can be a good convenience feature to silently (or with a warning) ignore missing file.
