On Wed, Mar 27, 2019 at 3:27 AM Michael Platings <mich...@platin.gs> wrote: > I think it's really important that we make this dead easy for everyone > to use. The ultimate in ease of use would be for git blame to > automatically pick up ignore settings without the user having to even > know that it's happening. But that breaks the principle of least > astonishment. The next simplest thing I can think of is to add a > configuration option blame.ignoreRevs which would have the same > effect, except the user has to opt in. > Barret has implemented blame.ignoreRevsFile, but I think the world > will be a more consistent and happier place if we dictate the location > that the revisions are loaded from, in the same way as .gitignore. > Deciding what that location should be is one of those bikeshed > arguments which is perhaps why Barret dodged it :)
And bikeshedding. Another good place to keep these revs is git-notes, which probably could result in faster lookups too and can be made visible in git-log. But that's in addition to --ignoreRevsFile, not replacing it. -- Duy
