{"thread":{"id":"38901","subject":"macblame - al alterntive to 'git blame'","startedAt":"2015-03-24T07:07:28Z","lastAt":"2015-03-24T14:10:30Z","messageCount":3,"participants":["Shenbaga Prasanna S","Duy Nguyen","Shenbaga Prasanna"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"258400","messageId":"CAFKdeLPb4HPJ4a5tvYXa2GEr-WK-Wra56m2vrU7-LheNDWp7iA@mail.gmail.com","threadId":"38901","inReplyTo":null,"subject":"macblame - al alterntive to 'git blame'","fromName":"Shenbaga Prasanna S","fromEmail":"prasanna.s@freshdesk.com","sentAt":"2015-03-24T07:07:28Z","receivedAt":"2015-03-24T07:07:28Z","isPatch":false,"sender":{"key":"prasanna.s@freshdesk.com","avatar":null},"body":"https://rubygems.org/gems/macblame/\n\ncheck this out.. and you can also contribute to the developement at,\n\nhttps://github.com/praserocking/macblame-gem\nor\nhttps://github.com/praserocking/macblame\n..\nhope this tool will be helpful to you all!\n\nThanks,\nPrasanna\n"},{"id":"258401","messageId":"CACsJy8ARVhgCOcM=XbELV-x_cNa8iGqMX6O2ouUp8UPq7xzcXw@mail.gmail.com","threadId":"38901","inReplyTo":"CAFKdeLPb4HPJ4a5tvYXa2GEr-WK-Wra56m2vrU7-LheNDWp7iA@mail.gmail.com","subject":"Re: macblame - al alterntive to 'git blame'","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2015-03-24T08:18:11Z","receivedAt":"2015-03-24T08:18:11Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Tue, Mar 24, 2015 at 2:07 PM, Shenbaga Prasanna S\n<prasanna.s@freshdesk.com> wrote:\n> https://rubygems.org/gems/macblame/\n>\n> check this out.. and you can also contribute to the developement at,\n>\n> https://github.com/praserocking/macblame-gem\n> or\n> https://github.com/praserocking/macblame\n> ..\n> hope this tool will be helpful to you all!\n\nIt would help if you pasted a sample output to see what it looks like.\nAlthough macblame script says \"macblame shows stats about the files\ntracked by git. It uses the output of 'git blame' and summarize it in\na cleaner and intuitive format\" so it's not really an alternative to\ngit-blame (you can't \"blame\" anybody by line with this). This is more\nlike \"git blame --stat\" (if that option existed)\n-- \nDuy\n"},{"id":"258485","messageId":"loom.20150324T150954-333@post.gmane.org","threadId":"38901","inReplyTo":"CACsJy8ARVhgCOcM=XbELV-x_cNa8iGqMX6O2ouUp8UPq7xzcXw@mail.gmail.com","subject":"Re: macblame - al alterntive to 'git blame'","fromName":"Shenbaga Prasanna","fromEmail":"prasanna.s@freshdesk.com","sentAt":"2015-03-24T14:10:30Z","receivedAt":"2015-03-24T14:10:30Z","isPatch":false,"sender":{"key":"prasanna.s@freshdesk.com","avatar":null},"body":"\nsample output..\n\nfor file Gemfile..\nContributor: Prasanna with 93.75 % contribution with 30 lines of code\nContributor: h4r1sh with 6.25 % contribution with 2 lines of code\n* * * * * * * * * * * * * * * * * * * * * * * * *\n\nand I built this tool by pipelining the output produced by 'git blame'\nand we use this tool for our internal purposes in our organisation\nwhere some files are edited by some 15 people and this will tell us\nwhom to catch if that files run into any problems (assuming largest\ncontributor knows what this file is upto).\n\nThanks,\nPrasanna\n"}]}