On Fri, Dec 3, 2010 at 3:29 PM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: > Eugene Sajine wrote: > >> Now as this is pretty much clear: don't you think that the information >> about one blob content changed during the merge should be present in >> the merge commit info? > > "git rev-list <revs> | git diff-tree --root -c --stdin" might give > some joy. > Allright, this is much closer now;) I used git rev-list HEAD | git diff-tree --root -c --stdin | grep <SHA1 of blob interest> (I need to read now about diff-tree) That gives me the output like this: ::SourceMode1 SourceMode2 resultMode Source1-SHA1 Source2-SHA1 resultingSHA1 MM path/to/file Now two questions: 1. a) Why this exact output is not provided in "git log --raw" or in "git whatchanged" for the merge commits? b) Can it be provided? 2. If 1b=no Is this the ultimate final solution to check if the blob has appeared somewhere in the history? Thanks! Eugene -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html