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

Re: Idea, Transparent commits, easier "code style" commits

From
Javier Domingo Cansino <javierdo1@gmail.com>
Date
Jul 6, 2014, 13:37 UTC
Message-ID
<CALZVapnofGirkPBFcgNp4-GZnrNAi3ZXDZA1LM-y3_LYQHksXA@mail.gmail.com>
In-Reply-To
<CAAwotL3vtkjVO5Zqz+w_gNSS0OAovUfukK8=-Df9K4ZybzNh0A@mail.gmail.com>
> They just have to look into the commit message and look for
> "#codestylefix" or whatever other string.

In many projects I have seen, they have a format for commits, such as "docs: Add support for XXX", "formatting: Space before parethesis and after comas", "tests: ...." and so on.

Maybe, being able to specify a RegExp would be the way to go, so that git blame did actually ignore those commits.

Previous: Andrius Bentkus
Message 4 of 4 in “Idea, Transparent commits, easier "code style" commits”
  1. Andrius BentkusJul 4, 2014
  2. Stefan BellerJul 4, 2014
  3. Andrius BentkusJul 6, 2014
  4. Javier Domingo CansinoJul 6, 2014

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.