author | Jeff King <peff@peff.net> | |
Wed, 7 Sep 2011 17:44:56 +0000 (13:44 -0400) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Thu, 8 Sep 2011 20:52:00 +0000 (13:52 -0700) | ||
commit | 7f6e275bc003e04fca63ae1058bb665078f72d7e | |
tree | f33c7d6fc07c0351a39f461305e4cf056e590b12 | tree | snapshot |
parent | 7ec0f31eec66b854a2ca856538723dea5f1c0ab7 | commit | diff |
for-each-ref: handle multiline subjects like --pretty
Generally the format of a git tag or commit message is:
subject
body body body
body body body
However, we occasionally see multiline subjects like:
subject
with multiple
lines
body body body
body body body
The rest of git treats these multiline subjects as something
to be concatenated and shown as a single line (e.g., "git
log --pretty=format:%s" will do so since f53bd74). For
consistency, for-each-ref should do the same with its
"%(subject)".
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Generally the format of a git tag or commit message is:
subject
body body body
body body body
However, we occasionally see multiline subjects like:
subject
with multiple
lines
body body body
body body body
The rest of git treats these multiline subjects as something
to be concatenated and shown as a single line (e.g., "git
log --pretty=format:%s" will do so since f53bd74). For
consistency, for-each-ref should do the same with its
"%(subject)".
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
builtin/for-each-ref.c | diff | blob | history | |
t/t6300-for-each-ref.sh | diff | blob | history |