+1
On Mon, Jan 14, 2013 at 11:27 AM, Marvin Addison
wrote:
> I would like to recommend that we adopt the recommended git convention
> of commit messages with the following format.
>
> ==TEMPLATE START===
> Short (50 chars or less) summary of changes
>
> More detailed explanatory t
+1
On Mon, Jan 14, 2013 at 1:27 PM, Marvin Addison wrote:
> I would like to recommend that we adopt the recommended git convention
> of commit messages with the following format.
>
> ==TEMPLATE START===
> Short (50 chars or less) summary of changes
>
> More detailed explanatory t
> That sounds reasonable for me. It sounds like for most people the
> difference would be not pressing enter after typing the JIRA issue :-)
Yup, and adding an empty line after the summary. So it is indeed
mostly about whitespace. It's a small change but has big implications
to readability for ma
That sounds reasonable for me. It sounds like for most people the
difference would be not pressing enter after typing the JIRA issue :-)
On Mon, Jan 14, 2013 at 1:27 PM, Marvin Addison wrote:
> I would like to recommend that we adopt the recommended git convention
> of commit messages with the
I would like to recommend that we adopt the recommended git convention
of commit messages with the following format.
==TEMPLATE START===
Short (50 chars or less) summary of changes
More detailed explanatory text, if necessary. Wrap it to about 72
characters or so. In some contex
