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

Re: blame --ignore-rev - repo-level ignore file

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Apr 18, 2020, 00:52 UTC
Message-ID
<20200418005253.GB121175@google.com>
In-Reply-To
<388B3B98-4929-4B4A-9167-3076CFDD0B5B@gmail.com>

(+Barret) Hi!

Enji Cooper wrote:
> Hi,
Show 18 quoted lines
> Given the increased number of C/C++ and python projects that both
> use git and a tool like black (python formatting tool), or
> clang-format (C/C++ tool, primarily), I would like to seriously
> consider revisiting the topic "blame --ignore-rev - repo-level
> ignore file” topic that was originally started by Terry Davis here
> [1] (quoted above for historical reference with the reply provided
> by Barret Rhoden).
>
> Having a default configuration that can be used with git instead of
> forcing end-users to set custom configs per repo clone would make it
> considerably easier for end-users: one could clone a repo, reformat
> code with an automated tool in a series of known commits, add
> ignored revisions to the file when using git blame, then make
> additional changes building off the automated reformatters' changes.
>
> I will be more than happy to submit patches to make this possible; I
> just need some guidance in terms of what’s required when
> contributing changes, etc.

The first question would be what you expect the end-to-end workflow to look like for users. What commands would they run? How would they discover them?

As for the general contribution process: https://www.kernel.org/pub/software/scm/git/docs/MyFirstContribution.html is a good starting point.

Thanks and hope that helps, Jonathan

> 1. https://marc.info/?l=git&m=156864623817929&q=mbox
Previous: Enji Cooper
Message 2 of 2 in “Re: blame --ignore-rev - repo-level ignore file”
  1. Enji CooperApr 17, 2020
  2. Jonathan NiederApr 18, 2020

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.