[FFmpeg-devel] [PATCH v2] doc/git-howto: be more strict about commit message formatting.

Gyan Doshi ffmpeg at gyani.pro
Mon Aug 16 16:43:34 EEST 2021



On 2021-08-16 06:50 pm, Nicolas George wrote:
> Gyan Doshi (12021-08-16):
>> "Details can be added, when necessary, separated by an empty line. These
>> lines should not exceed 72 characters, except when containing code."
> Thanks, it is better. I have slightly amended it to:
>
> The first line must contain the context, a colon and a very short
> summary of what the commit does. Details can be added, if necessary,
> separated by an empty line. These details should not exceed 60-72 characters

The maximum, if specified, should be a single value.

> per line, except when containing code.
>
>> enohgh --> enough
> Fixed, thanks.
>
>> Isn't the first line just the log message referred to above? If so, this and
>> the next line and a half seem repetitive.
> No, "log" is just an obsolete wording inherited from the SVN habits,
> AFAIU, "log message" and "commit message" are the same thing and cover
> the whole message.
>
> I have called the first line the summary. I see some people call it the
> subject.
>
>> Seems OK. Don't mind if I rephrase, later on.
> I will leave some more time then.

Don't hold up on my account. I'll do it later when I survey that whole 
page for corrections and improvements.

Regards,
Gyan


More information about the ffmpeg-devel mailing list