git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC PATCH 0/1] Fuzzy blame

From
Duy Nguyen <pclouds@gmail.com>
Date
Mar 27, 2019, 06:36 UTC
Message-ID
<CACsJy8D8yBK9p9Rgy+wk8cMfPLG7qanvGA-LcmmHmjbaMnvBLQ@mail.gmail.com>
In-Reply-To
<CAJDYR9RVz6ZKQ-vdC8O3LYZnGeBcGHCRtL0m6UoRrKDBsUoFOw@mail.gmail.com>
On Wed, Mar 27, 2019 at 3:27 AM Michael Platings <michael@platin.gs> wrote:
Show 12 quoted lines
> 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
Previous: Michael PlatingsNext: Michael Platings
Message 10 of 14 in “Fuzzy blame”
  1. 0/1 Fuzzy blamemichael@platin.gs, Mar 24, 2019
  2. 1/1 Fuzzy blamemichael@platin.gs, Mar 24, 2019
  3. Junio C HamanoMar 25, 2019
  4. Michael PlatingsMar 25, 2019
  5. Barret RhodenMar 25, 2019
  6. Michael PlatingsMar 25, 2019
  7. Jeff KingMar 25, 2019
  8. Jacob KellerMar 26, 2019
  9. Michael PlatingsMar 26, 2019
  10. Duy NguyenMar 27, 2019
  11. Michael PlatingsMar 27, 2019
  12. Duy NguyenMar 27, 2019
  13. Barret RhodenApr 3, 2019
  14. Michael PlatingsApr 3, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.