[gnunet] 01/03: Fix git commit message preparation to properly include hints.

[gnunet]

This is an automated email from the git hooks/post-receive script.

martin-schanzenbach pushed a commit to branch master
in repository gnunet.

commit 2161f34f8cd4d4250248554c0e1786ad4c45de16
Author: Martin Schanzenbach <schanzen@gnunet.org>
AuthorDate: Wed Feb 1 18:56:39 2023 +0900

    Fix git commit message preparation to properly include hints.
---
 contrib/conf/prepare-commit-msg | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contrib/conf/prepare-commit-msg b/contrib/conf/prepare-commit-msg
index 8acca9e38..a95f29430 100755
--- a/contrib/conf/prepare-commit-msg
+++ b/contrib/conf/prepare-commit-msg
@@ -27,7 +27,7 @@ done
 if [ -z "$COMMIT_SOURCE" ];
 then
   hint=$(cat "$COMMIT_MSG_FILE")
-  echo -e "# Our commit subject format policy is:\n# <subsystem>: 
<description>\n# Adding 'Issue #1234'/'Fixes #1234' into the description will 
automatically update/resolve issue #1234 in mantis." >> "$COMMIT_MSG_FILE"
+  echo -e "# Our commit subject format policy is:\n# <subsystem>: 
<description>\n# Adding 'Issue #1234'/'Fixes #1234' into the description will 
automatically update/resolve issue #1234 in mantis." > "$COMMIT_MSG_FILE"
   if [ $RET = 1 ];
   then
     echo -e "# Your commit includes staged changes that indicate an API change 
which requires a NEWS line." >> "$COMMIT_MSG_FILE"

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.