summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 50ac740)
raw | patch | inline | side by side (parent: 50ac740)
author | Junio C Hamano <junkio@cox.net> | |
Wed, 19 Apr 2006 21:58:24 +0000 (14:58 -0700) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Wed, 19 Apr 2006 22:37:40 +0000 (15:37 -0700) |
Several <<< or === or >>> characters at the beginning of a line
is very likely to be leftover conflict markers from a failed
automerge the user resolved incorrectly, so detect them.
As usual, this can be defeated with "git commit --no-verify" if
you really do want to have those files, just like changes that
introduce trailing whitespaces.
Signed-off-by: Junio C Hamano <junkio@cox.net>
is very likely to be leftover conflict markers from a failed
automerge the user resolved incorrectly, so detect them.
As usual, this can be defeated with "git commit --no-verify" if
you really do want to have those files, just like changes that
introduce trailing whitespaces.
Signed-off-by: Junio C Hamano <junkio@cox.net>
templates/hooks--pre-commit | patch | blob | history |
index 43d3b6ef4a0e515cdc8d9874a81029d4d9425f64..723a9ef210bb84c217026c2cdf9d30661f64447b 100644 (file)
if (/^\s* /) {
bad_line("indent SP followed by a TAB", $_);
}
+ if (/^(?:[<>=]){7}/) {
+ bad_line("unresolved merge conflict", $_);
+ }
}
}
exit($found_bad);