Summary: Add Bugfix-for line to prepare-commit-msg

Detail: This reminds us to tag commits that should be considered for a bugfix
release, making them easier to find/apply and less likely to slip through the
cracks. Individual committers really should know best which things need to be
pushed as an immediate bugfix anyway, this makes it easy to tag things as such.

Signed-off-by: Marcus Sorensen <marcus@betterservers.com> 1352308027 -0700
This commit is contained in:
Marcus Sorensen 2012-11-07 10:07:07 -07:00
parent b42f3f53d8
commit 6e23cad126

View File

@ -64,6 +64,7 @@ cat <<EOF > $file
# Detail: Multi-line description, followed by blank line
#
# BUG-ID: CLOUDSTACK-9999
# Bugfix-for: 4.0 (a branch that this should be considered for in a bugfix release)
# Reviewed-by: Bar Barlington <bar@example.com>, Foo McFooson <foo@example.com>
# Reported-by: Baz Bazelli <baz@example.com>
# Signed-off-by: You <you@yourdomain.com>
@ -76,7 +77,8 @@ SOB=$(git var GIT_AUTHOR_IDENT)
sed -i "1s/^/################################# 80 chars #####################################\n\
Summary: \n\n\
Detail: \n\n\
BUG-ID : \n\
BUG-ID: \n\
Bugfix-for: \n\
Reviewed-by: \n\
Reported-by: \n\
Signed-off-by: ${SOB}\n\n/" $file