author | Junio C Hamano <gitster@pobox.com> | |
Thu, 8 Apr 2010 17:17:17 +0000 (10:17 -0700) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Fri, 9 Apr 2010 06:13:48 +0000 (23:13 -0700) | ||
commit | 4f62c2bc577bbb85b65f3261c7fab7ef74def4cd | |
tree | f741d67400d05f93da6ca1edc46b880482543d17 | tree | snapshot |
parent | b0e621adfd5a60b7cbe95e59f09c87f0870321cb | commit | diff |
log.decorate: only ignore it under "log --pretty=raw"
Unlike notes that are often multi-line and disrupting to be placed in many
output formats, a decoration is designed to be a small token that can be
tacked after an existing line of the output where a commit object name sits.
Disabling log.decorate for something like "log --oneline" would defeat the
purpose of the configuration.
We _might_ want to change it further in the future to force scripts that
do not want to be broken by random end user configurations to explicitly
say "log --no-decorate", but that would be an incompatible change that
needs the usual multi-release-cycle deprecation process.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Unlike notes that are often multi-line and disrupting to be placed in many
output formats, a decoration is designed to be a small token that can be
tacked after an existing line of the output where a commit object name sits.
Disabling log.decorate for something like "log --oneline" would defeat the
purpose of the configuration.
We _might_ want to change it further in the future to force scripts that
do not want to be broken by random end user configurations to explicitly
say "log --no-decorate", but that would be an incompatible change that
needs the usual multi-release-cycle deprecation process.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
builtin-log.c | diff | blob | history | |
t/t4202-log.sh | diff | blob | history |