projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 3368edd) | patch
docs: clarify meaning of -M for git-log
authorJeff King <peff@peff.net>
Sat, 8 May 2010 04:44:34 +0000 (00:44 -0400)
committerJunio C Hamano <gitster@pobox.com>
Wed, 19 May 2010 04:32:41 +0000 (21:32 -0700)
commit7ffad2501489690edd9335fdd1e69c05699767e3
treed23dcd508bd6354b9d979555973b7b0eccebbdcbtree | snapshot
parent3368edd4cda6306d524e10758e2c5a187dcd4ba6commit | diff
docs: clarify meaning of -M for git-log

As an option to the "diff" family, it is fairly obvious what
"detect renames" means. However, for revision traversal, the
"-M" option is just included in the long list of options,
with no indication that it is about showing renames in diffs
versus following renames. Let's make it more explicit.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/diff-options.txt diff | blob | history
Git—the stupid content tracker