On Sun, Aug 18, 2013 at 6:33 PM, Zhan Jianyu <nasa4...@gmail.com> wrote:
>   Such a requirement came into my mind when I am tracking a gloomy C
> struct , with lengthy list of elements which are either elaborated or
> opaque. So I use git blame to track it down and found that its
> original version is quite simple and intuitive. So I think I could
> just slice out every snapshot of this struct, reading every changelog
> , to get a better knowledge of what it is and why it should be like
> this.
> It seems quite helpful but the process is quite cumbersome. So I
> wonder if there is already some mechanism fulfilling my requirement in
> Git.  If it doesn't,  would it be worthy adding one ?

It's already merged to git.git's master quite recently in
ed73fe56428eecd2b635473f6a517a183c4713a3 (back in June).

You'd invoke git log like this:

    $ git log -L :struct_or_function_name:filename.c

and it will show you the commits and the specific hunks that affect
the struct or function name.

It's still a bit rough on the edges, for example, doing the following
in git.git:

    $ git log -L :rev_cmdline_info:revision.h

Shows three commits (a765499, ca92e59 and 281eee4) where the second
one does not touch the struct at all (if you do "git show ca92e59" you
might gain an insight as to how -L works).

But that is not to say that it's not good. The gain really shadows the

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