On Mon, Jan 27, 2014 at 7:45 PM, David Kastrup <d...@gnu.org> wrote:
> The git blame manual page talks about using git blame --reverse to
> figure out when a particular change disappeared, but I cannot make it
> produce anything useful regardless of what range I give it.  Using
> --root delivers a different state of uselessness.
> Can anyone give a recipe for using git blame --reverse on the Git code
> base for figuring out anything of relevance?

I rarely use blame, but the commit that introduces --reverse seems to
have an example. See 85af792 (git-blame --reverse - 2008-04-02)
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to