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

Re: macblame - al alterntive to 'git blame'

From
SPShenbaga Prasanna <prasanna.s@freshdesk.com>
Date
Mar 24, 2015, 14:10 UTC
Message-ID
<loom.20150324T150954-333@post.gmane.org>
In-Reply-To
<CACsJy8ARVhgCOcM=XbELV-x_cNa8iGqMX6O2ouUp8UPq7xzcXw@mail.gmail.com>
sample output..
for file Gemfile..
Contributor: Prasanna with 93.75 % contribution with 30 lines of code
Contributor: h4r1sh with 6.25 % contribution with 2 lines of code
* * * * * * * * * * * * * * * * * * * * * * * * *

and I built this tool by pipelining the output produced by 'git blame' and we use this tool for our internal purposes in our organisation where some files are edited by some 15 people and this will tell us whom to catch if that files run into any problems (assuming largest contributor knows what this file is upto).

Thanks, Prasanna

Previous: Duy Nguyen
Message 3 of 3 in “macblame - al alterntive to 'git blame'”
  1. Shenbaga Prasanna SMar 24, 2015
  2. Duy NguyenMar 24, 2015
  3. Shenbaga PrasannaMar 24, 2015

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.