On 05.04.2017 00:31, Brian Brooks wrote: > On 04/04 14:53:23, Bill Fischofer wrote: >> On Tue, Apr 4, 2017 at 2:45 PM, Brian Brooks <brian.bro...@arm.com> wrote: >>> On 04/04 21:55:06, Maxim Uvarov wrote: >>>> this patch should be not part of this serries and can go to master as >>>> standalone patch. >>> >>> Can you help to cherry pick such patches to master? They need to remain >>> in this patch series until they are cherry picked to master and master >>> is sync'd into api-next. At that point I can drop them from this patch >>> series. Does this make sense? >>> >>>> No need of camel case is shor description. Long >>>> description in git comment is required. >>> >>> I'm not sure what to put for the long description because the short >>> description is succinct enough. Can you provide an example for this >>> specific commit? >> >> Maxim is just saying is that the ODP convention is that the short log >> (first line of the commit message) is always all lower-case. > > I understand that, but I do not understand why a commit must include a > long description in addition to the short description. If the short > description is succinct enough, why require more text?
Cause it is not sufficient, as you can see from my previous e-mails. -- With best wishes Dmitry
