On Tue, 9 May 2006, Bertrand Jacquin wrote: > On 5/9/06, Linus Torvalds <torvalds@xxxxxxxx> wrote: > > > > Ie you could probably more easily parse the data from something like > > > > git show -B --patch-with-stat --pretty=fuller $commit > > > > Is there a way to track merge like that ? Documentation is not very > clear and near from empty. Sure. If you want to track merges and get their patches, add the "--cc" flag, which tells git to use the "conflict combination patch" that shows any visible conflicts. (NOTE NOTE NOTE! This is _not_ the same as showing what conflicted: if you edited the result to match one of the original branches, it will be quiet in --cc, but if the result of a conflict was something that was in _neither_ branch, it will be shown! So most clean merges will not show any conflict diff at all, but the diffstat will be shown against the "first parent"). And you probably don't want to abbreviate the parent commit SHA1's (which are shown for merges, but not regular commits), so add "--no-abbrev". If you want to show parents for _all_ commits, you could do something like git show --no-abbrev --cc -C --patch-with-stat --pretty=fuller --parents | sed '1 s/commit [0-9a-f]*/\0\nParents: / ; /^Merge: / d' which removes a potential "Merge: " line in favour of listing the parents on a "Parents:" line, and which also shows merges nicely. That said, the diffstat for merges is usually just a lot of noise. It's sometimes nice (you've merged from a topic branch), but if you have merged from the mainline _into_ a topic branch, it's just annoying. So the above is just a wild suggestion. Caveat emptor. Linus - : 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