One of the new cvs's features is to be able to run a checker on the

log messages after they've been entered.  This is more flexible than
using the editinfo script since it works for all log message types
and doesn't have to deal with trying to run the editor for the user.

The problem is that the verifymsg script can't modify the file like
editinfo can, which makes it useless for cleaning up the message (as is
needed for remote commits etc).  This change causes the verifymsg handler
to read back the message after the verify script has run and returned an
"OK" exit code.

1 files changed, 3 insertions, 3 deletions

diff --git a/contrib/cvs/src/commit.c b/contrib/cvs/src/commit.c
index c43e35f..7ae1ce7 100644
--- a/contrib/cvs/src/commit.c
+++ b/contrib/cvs/src/commit.c
@@ -486,7 +486,7 @@ commit (argc, argv)
 	/* Run the user-defined script to verify/check information in
 	 *the log message
 	 */
-	do_verify (message, (char *)NULL);  	
+	do_verify (&message, (char *)NULL);  	
 
 	/* We always send some sort of message, even if empty.  */
 	option_with_arg ("-m", message);
@@ -1110,7 +1110,7 @@ commit_fileproc (callerdat, finfo)
 	got_message = 1;
 	if (use_editor)
 	    do_editor (finfo->update_dir, &message, finfo->repository, ulist);
-	do_verify (message, finfo->repository);  
+	do_verify (&message, finfo->repository);  
     }
 
     p = findnode (cilist, finfo->file);
@@ -1400,7 +1400,7 @@ commit_direntproc (callerdat, dir, repos, update_dir, entries)
     got_message = 1;
     if (use_editor)
 	do_editor (update_dir, &message, real_repos, ulist);
-    do_verify (message, real_repos);  
+    do_verify (&message, real_repos);  
     free (real_repos);
     return (R_PROCESS);
 }