Reg git commits

[Rakesh Radhakrishnan <ra...@gmail.com>]

Hi All,

I was looking at the git commits and commit log messages. It would be good
if we could follow common patterns for the "commit log message". Following
are two suggestions, probably we could choose one of them and all can
follow the same. Welcome if any other better options.

*Commit log msg pattern-1 :-*

Jira id: jira subject line. Contributed by Wang Gang
For example,
MNEMONIC-5: Refactor code for package com.intel.bigdatamem. (Contributed by
Wang Gang)

OR

*Commit log msg pattern-2 :-*

Jira id: jira subject line (contributor_name via committer_user_name)
For example,
MNEMONIC-5: Refactor code for package com.intel.bigdatamem (Wang Gang via
garyw)


Thanks,
Rakesh

Re: Reg git commits

["Gangumalla, Uma" <um...@intel.com>]

Thanks for raising this point Rakesh.

Agree we should follow specific pattern, which would look good if we want
to create any release notes etc from git log later.

Below pattern should be fine:
Jira id: jira subject line. Contributed by Wang Gang


Regards,
Uma

On 4/9/16, 10:00 AM, "Rakesh Radhakrishnan" <ra...@gmail.com>
wrote:

>Hi All,
>
>I was looking at the git commits and commit log messages. It would be good
>if we could follow common patterns for the "commit log message". Following
>are two suggestions, probably we could choose one of them and all can
>follow the same. Welcome if any other better options.
>
>*Commit log msg pattern-1 :-*
>
>Jira id: jira subject line. Contributed by Wang Gang
>For example,
>MNEMONIC-5: Refactor code for package com.intel.bigdatamem. (Contributed
>by
>Wang Gang)
>
>OR
>
>*Commit log msg pattern-2 :-*
>
>Jira id: jira subject line (contributor_name via committer_user_name)
>For example,
>MNEMONIC-5: Refactor code for package com.intel.bigdatamem (Wang Gang via
>garyw)
>
>
>Thanks,
>Rakesh