Make sure that the user enters a commit message, and bomb out if

not.  This doesn't fix all cases of this because cvs doesn't invoke
loginfo/logcheck if the log message is completely blank.  Usually
there is an rcstemple in there though, so we'll catch most instances.

1 files changed, 7 insertions, 0 deletions

diff --git a/CVSROOT/logcheck b/CVSROOT/logcheck
index 66fcb1539cf7..f50bdd74fe82 100755
--- a/CVSROOT/logcheck
+++ b/CVSROOT/logcheck
@@ -99,6 +99,13 @@ while ($j >= 0) {
 }
 
 
+# Make sure that there is some content in the log message.
+# XXX Note that logcheck isn't evoked if the log message is
+# completely empty.  This is a bug in cvs.
+my $log = "@log_in";
+die "Log message contains no content!\n" if $log =~ /^\s*$/;
+
+
 # Write the modified log file back out.
 my $tmpfile = $filename . "tmp";
 open OUT, "> $tmpfile" or