Yes, another interesting question about how to tie the process together
is finding a way to connect between fixes and the tests that they
address. I haven't found something automatic (yet) but putting
appropriate QA tags and just writing the tests in the body of the
message already helps an external tester verify that it does what it is
supposed to.

Might also help prevent multiple fixes to the same bug, which I think
might be the case here...

Daniel

Andreas Raab <andreas.raab at gmx.de> wrote:
> Provides ten missing #hash implementations as pointed out by the base image
> tests thus removing the number of failed tests by ten."