{"thread":{"id":"35740","subject":"What's with git blame --reverse ?","startedAt":"2014-01-27T12:45:32Z","lastAt":"2014-01-27T14:15:47Z","messageCount":2,"participants":["David Kastrup","Duy Nguyen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"233817","messageId":"87y5218ufn.fsf@fencepost.gnu.org","threadId":"35740","inReplyTo":null,"subject":"What's with git blame --reverse ?","fromName":"David Kastrup","fromEmail":"dak@gnu.org","sentAt":"2014-01-27T12:45:32Z","receivedAt":"2014-01-27T12:45:32Z","isPatch":false,"sender":{"key":"dak@gnu.org","avatar":"https://avatars.githubusercontent.com/u/52141349?v=4"},"body":"\nThe git blame manual page talks about using git blame --reverse to\nfigure out when a particular change disappeared, but I cannot make it\nproduce anything useful regardless of what range I give it.  Using\n--root delivers a different state of uselessness.\n\nCan anyone give a recipe for using git blame --reverse on the Git code\nbase for figuring out anything of relevance?\n\nSince I am in the process of rewriting git-blame, of course I want to\nverify that everything works, but while I achieve the same results, they\nseem fabulously useless before and after my rewrite.\n\n-- \nDavid Kastrup\n"},{"id":"233818","messageId":"CACsJy8CCZxKYW=AAz-OsKxrjNo2NyqUQF=NJXH20hv4miFUs8g@mail.gmail.com","threadId":"35740","inReplyTo":"87y5218ufn.fsf@fencepost.gnu.org","subject":"Re: What's with git blame --reverse ?","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2014-01-27T14:15:47Z","receivedAt":"2014-01-27T14:15:47Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Mon, Jan 27, 2014 at 7:45 PM, David Kastrup <dak@gnu.org> wrote:\n>\n> The git blame manual page talks about using git blame --reverse to\n> figure out when a particular change disappeared, but I cannot make it\n> produce anything useful regardless of what range I give it.  Using\n> --root delivers a different state of uselessness.\n>\n> Can anyone give a recipe for using git blame --reverse on the Git code\n> base for figuring out anything of relevance?\n\nI rarely use blame, but the commit that introduces --reverse seems to\nhave an example. See 85af792 (git-blame --reverse - 2008-04-02)\n-- \nDuy\n"}]}