diff options
| author | Brandon Casey <drafnel@gmail.com> | 2013-02-19 04:17:06 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2013-02-19 17:30:50 (GMT) |
| commit | a24a41ea9a928ccde2db074ab0835c4817223c9d (patch) | |
| tree | 01c2ec81dc2213601ef0eac8467068e99747507f /builtin/commit.c | |
| parent | 5b012c80a165236dde57c386fd62465e9137b2ce (diff) | |
| download | git-a24a41ea9a928ccde2db074ab0835c4817223c9d.zip git-a24a41ea9a928ccde2db074ab0835c4817223c9d.tar.gz git-a24a41ea9a928ccde2db074ab0835c4817223c9d.tar.bz2 | |
git-commit: only append a newline to -m mesg if necessary
Currently, git will append two newlines to every message supplied via
the -m switch. The purpose of this is to allow -m to be supplied
multiple times and have each supplied string become a paragraph in the
resulting commit message.
Normally, this does not cause a problem since any trailing newlines will
be removed by the cleanup operation. If cleanup=verbatim for example,
then the trailing newlines will not be removed and will survive into the
resulting commit message.
Instead, let's ensure that the string supplied to -m is newline terminated,
but only append a second newline when appending additional messages.
Fixes the test in t7502.
Signed-off-by: Brandon Casey <drafnel@gmail.com>
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/commit.c')
| -rw-r--r-- | builtin/commit.c | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/builtin/commit.c b/builtin/commit.c index 3348aa1..d21d07a 100644 --- a/builtin/commit.c +++ b/builtin/commit.c @@ -124,8 +124,10 @@ static int opt_parse_m(const struct option *opt, const char *arg, int unset) if (unset) strbuf_setlen(buf, 0); else { + if (buf->len) + strbuf_addch(buf, '\n'); strbuf_addstr(buf, arg); - strbuf_addstr(buf, "\n\n"); + strbuf_complete_line(buf); } return 0; } |