{"thread":{"id":"53979","subject":"git blame --ignore-rev to accept tree objects","startedAt":"2020-08-04T07:40:48Z","lastAt":"2020-08-04T15:19:29Z","messageCount":2,"participants":["Amir Yalon","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"402798","messageId":"9e184f84-9658-4562-88ea-50039b19aea7@www.fastmail.com","threadId":"53979","inReplyTo":null,"subject":"git blame --ignore-rev to accept tree objects","fromName":"Amir Yalon","fromEmail":"amiryal-mljwnltxmo@yxejamir.net","sentAt":"2020-08-04T07:40:16Z","receivedAt":"2020-08-04T07:40:48Z","isPatch":false,"sender":{"key":"amiryal-mljwnltxmo@yxejamir.net","avatar":null},"body":"Dear list members,\n\nIn the manual entry for blame.ignoreRevsFile in git-config(1) it says “unabbreviated object name”, which misled me into thinking I could specify tree objects rather than commit objects. This got me thinking, how useful it could be, to be able to include detailed instructions how to ignore a particular commit *in its own commit message*. Right now, it is practically impossible to do, because one can’t know the commit object name in advance. However, once the tree object name is known, it’s easy to include in the commit message.\n\nHow practical would it be to implement this feature? How bad could it be, if some unrelated commits with the same tree would be skipped unintentionally by git-blame as a result?\n\nRegards,\nAmir\n"},{"id":"402818","messageId":"xmqq4kpitp54.fsf@gitster.c.googlers.com","threadId":"53979","inReplyTo":"9e184f84-9658-4562-88ea-50039b19aea7@www.fastmail.com","subject":"Re: git blame --ignore-rev to accept tree objects","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2020-08-04T15:19:19Z","receivedAt":"2020-08-04T15:19:29Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Amir Yalon\" <amiryal-mljwnltxmo@yxejamir.net> writes:\n\n> How practical would it be to implement this feature? How bad could it be, if some unrelated commits with the same tree would be skipped unintentionally by git-blame as a result?\n\nI would say it would be horrible, if the instruction to skip a wrong\ncommit is baked into the commit object and cannot be corrected\nwithout rewriting history.\n"}]}