Fix bug in BK trigger for sending changes to InnoDB devs.

parent 52502879
...@@ -345,10 +345,10 @@ changes are in a clone of a $mysql_version tree. ...@@ -345,10 +345,10 @@ changes are in a clone of a $mysql_version tree.
EOF EOF
} }
print SENDMAIL "\n"; print SENDMAIL "\n";
print SENDMAIL qx(bk changes -r+); print SENDMAIL qx(bk changes -r'$cset');
print SENDMAIL "$description"; print SENDMAIL "$description";
print SENDMAIL "The complete ChangeSet diffs follow.\n\n"; print SENDMAIL "The complete ChangeSet diffs follow.\n\n";
print SENDMAIL qx(bk rset -r+ -ah | bk gnupatch -h -dup -T); print SENDMAIL qx(bk rset -r'$cset' -ah | bk gnupatch -h -dup -T);
close_or_warn(SENDMAIL, "$sendmail -t") close_or_warn(SENDMAIL, "$sendmail -t")
or return undef; or return undef;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment