More thorough commit messages are a big help in generating correct and complete release notes. Feel free to include developer motivation or user oriented information if appropriate. It helps others follow your contribution and makes it easier to build on.
On 9/9/2011 1:34 PM, Chris Marshall wrote:
From the "Git Community Book", with some numbers addedby me: "A note on commit messages: Though not required, it's a good idea to [1] begin the commit message with a single short (less than 50 character) line summarizing the change, [2] followed by a blank line [3] and then a more thorough description. Tools that turn commits into email, for example, use the first line on the Subject: line and the rest of the commit message in the body."
_______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
