From c936ba171929b43963afd68dd66944199e2351f4 Mon Sep 17 00:00:00 2001 From: joey Date: Sat, 24 Mar 2007 15:14:53 +0000 Subject: * Fix mercurial backend to deal with empty commit messages. --- doc/bugs/Http_error_500_when_using_mercurial_backend.mdwn | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) (limited to 'doc/bugs/Http_error_500_when_using_mercurial_backend.mdwn') diff --git a/doc/bugs/Http_error_500_when_using_mercurial_backend.mdwn b/doc/bugs/Http_error_500_when_using_mercurial_backend.mdwn index 5015b6290..db49f1e4a 100644 --- a/doc/bugs/Http_error_500_when_using_mercurial_backend.mdwn +++ b/doc/bugs/Http_error_500_when_using_mercurial_backend.mdwn @@ -19,4 +19,10 @@ Here is a quick patch, partialy copying the svn backend. + $message="web commit by Anonymous".(length $message ? ": $message" : ""); } - $message = possibly_foolish_untaint($message); \ No newline at end of file + $message = possibly_foolish_untaint($message); + +> The svn backend puts the user info in the message because that's the only +> way to store the user info, unlike with mercurial. The svn plugin also +> removes that info when getting the RecentChanges info. Since mercurial +> does not do that, it seemed better to me to test for an empty message and +> set it to a dummy commit string, which I've [[done]]. --[[Joey]] -- cgit v1.2.3