Jonathan Nieder wrote: > Martin Langhoff wrote: >> On Mon, May 13, 2013 at 2:55 PM, Jonathan Nieder <jrnie...@gmail.com> wrote: > >>> My experience is the opposite. I wonder "What did the author of this >>> nonsense comment mean?" or "What is the purpose of this strange >>> condition in this if () statement?". Then "git log -S" finds the >>> culprit >> >> Only if that if () statement looks that way from a single commit. >> That's my point. If the line code bit you are looking at is the result >> of several changes, your log -S will grind a while and find you >> nothing. > > Well, no, it should find the final change that brought it into the > current form. Just like "git blame".
I still don't know exactly what -G and -S do. The documentation can be improved, no? A nice example would definitely help. Thanks. -- 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
