[PATCH 0/3] Showing merges easier with "git log"

This is a combination of two closely related topics.

 - The second patch is my long-time pet peeve (it is even on the
   leftover-bits list at git-blame blog).  When inspecting a branch,
   I often type "git log --first-parent --cc master..", and then
   realize that I need to give "-p" to actually view the condensed
   patch.  We do the same for "log -c" (combined but not desified
   form).

 - The third one is about "git log --cc master..", with which the
   user is clearly telling us that s/he wants to see interesting
   changes for both single-parent commits and for merges (otherwise
   s/he wouldn't be saying "--cc" in the first place).  Even with
   the second one that makes "--cc" imply "-p" unless another patch
   output format (e.g. "--raw") was asked, you'd need "-m", which
   was irritating.

The latter was inspired by a recent discussion, most notably

   http://thread.gmane.org/gmane.comp.version-control.git/273937/focus=273988

but implements it with a much less UI impact. Tweaking "git log -p" has a lot of fallout---interested parties can try it out and how two tests in t4xxx series break. Doing this for "log --cc" is conceptually cleaner, as "-p" does not tell us what the user wants to see for merges (nothing? first-parent diff? pairwise diff? combined?), but "--cc" is a clear indication that dense combined patch is desired.

Note that this conflicts with 'tr/remerge-diff' topic that has been stalled on 'pu' for quite some time. I'll tentatively drop that other topic before pushing out today's integration result. People who are interested in that topic may want to help resurrect and reroll it. Hint, hint...

Junio C Hamano (3):
  log: rename "tweak" helpers
  log: when --cc is given, default to -p unless told otherwise
  log: show merge commit when --cc is given

 builtin/log.c | 19 ++++++++++++++-----
 1 file changed, 14 insertions(+), 5 deletions(-)