{"thread":{"id":"53251","subject":"Re: blame --ignore-rev - repo-level ignore file","startedAt":"2020-04-17T23:39:54Z","lastAt":"2020-04-18T00:52:58Z","messageCount":2,"participants":["Enji Cooper","Jonathan Nieder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"395676","messageId":"388B3B98-4929-4B4A-9167-3076CFDD0B5B@gmail.com","threadId":"53251","inReplyTo":"B2997F0D-AEEE-4431-85B8-98831ACF85B6@gmail.com","subject":"Re: blame --ignore-rev - repo-level ignore file","fromName":"Enji Cooper","fromEmail":"yaneurabeya@gmail.com","sentAt":"2020-04-17T23:39:50Z","receivedAt":"2020-04-17T23:39:54Z","isPatch":false,"sender":{"key":"yaneurabeya@gmail.com","avatar":"https://gravatar.com/avatar/48933e620edcd6784a0d640769b899693e42bce6c259e4a41bc612754a41285d?d=mp&s=160"},"body":"Hi,\n\tGiven 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).\n\tHaving 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.\n\tI 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.\nThank you,\n-Enji\t\n\n1. https://marc.info/?l=git&m=156864623817929&q=mbox\n"},{"id":"395677","messageId":"20200418005253.GB121175@google.com","threadId":"53251","inReplyTo":"388B3B98-4929-4B4A-9167-3076CFDD0B5B@gmail.com","subject":"Re: blame --ignore-rev - repo-level ignore file","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2020-04-18T00:52:53Z","receivedAt":"2020-04-18T00:52:58Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"(+Barret)\nHi!\n\nEnji Cooper wrote:\n\n> Hi,\n\n> Given the increased number of C/C++ and python projects that both\n> use git and a tool like black (python formatting tool), or\n> clang-format (C/C++ tool, primarily), I would like to seriously\n> consider revisiting the topic \"blame --ignore-rev - repo-level\n> ignore file” topic that was originally started by Terry Davis here\n> [1] (quoted above for historical reference with the reply provided\n> by Barret Rhoden).\n>\n> Having a default configuration that can be used with git instead of\n> forcing end-users to set custom configs per repo clone would make it\n> considerably easier for end-users: one could clone a repo, reformat\n> code with an automated tool in a series of known commits, add\n> ignored revisions to the file when using git blame, then make\n> additional changes building off the automated reformatters' changes.\n>\n> I will be more than happy to submit patches to make this possible; I\n> just need some guidance in terms of what’s required when\n> contributing changes, etc.\n\nThe first question would be what you expect the end-to-end workflow\nto look like for users.  What commands would they run?  How would\nthey discover them?\n\nAs for the general contribution process:\nhttps://www.kernel.org/pub/software/scm/git/docs/MyFirstContribution.html\nis a good starting point.\n\nThanks and hope that helps,\nJonathan\n\n> 1. https://marc.info/?l=git&m=156864623817929&q=mbox\n"}]}