author | Junio C Hamano <junkio@cox.net> | |
Wed, 12 Apr 2006 18:45:18 +0000 (11:45 -0700) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Wed, 12 Apr 2006 18:45:18 +0000 (11:45 -0700) | ||
commit | 475443c8489d9167b944367d8ec8bfef77bee0a5 | |
tree | f7af3152e028708b74690a228915671fd3a7f774 | tree | snapshot |
parent | 684958ae6162c593bd90ba893271ffb2381c3c44 | commit | diff |
git-commit: do not muck with commit message when no_edit is set.
Spotted by Linus and Darrin Thompson. When we took a commit
message from -F <file> with an incomplete line, we appended "git
status" output, which ended up attaching a lone "#" at the end.
We still need the "do we have anything to commit?" check by
running "status" (which has to know what to do in different
cases with -i/-o/-a), but there is no point appending its output
to the proposed commit message given by the user.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Spotted by Linus and Darrin Thompson. When we took a commit
message from -F <file> with an incomplete line, we appended "git
status" output, which ended up attaching a lone "#" at the end.
We still need the "do we have anything to commit?" check by
running "status" (which has to know what to do in different
cases with -i/-o/-a), but there is no point appending its output
to the proposed commit message given by the user.
Signed-off-by: Junio C Hamano <junkio@cox.net>
git-commit.sh | diff | blob | history |