http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9009

--- Comment #14 from Jared Camins-Esakov <[email protected]> ---
(In reply to comment #13)
> I always include my test plan in a comment so we don't have them mucking up
> the git log. I also didn't include a commit message because I thought the
> title was self explanatory.

If the test plan on the bug is clearly labelled "test plan:" or "to test:" I
will probably use it. However, including the test plan in the commit message
does increase the chances of the patch getting pushed to Master quickly. Marc's
commit message is absolutely perfect, because it tells me in one second exactly
what the patch does (adds two sysprefs), how to test it, and what tests Marc
performed.

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to