Re: Template for commit messages
От | Tom Lane |
---|---|
Тема | Re: Template for commit messages |
Дата | |
Msg-id | 1792.1453992745@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Template for commit messages (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Template for commit messages
Re: Template for commit messages |
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > On Thu, Jan 28, 2016 at 8:04 AM, Tomas Vondra > <tomas.vondra@2ndquadrant.com> wrote: >> Why can't we do both? That is, have a free-form text with the nuances, and >> then Reviewed-By listing the main reviewers? The first one is for humans, >> the other one for automated tools. > I'm not objecting to or endorsing any specific proposal, just asking > what we want to do about this. I think the trick if we do it that way > will be to avoid having it seem like too much duplication, but there > may be a way to manage that. FWIW, I'm a bit suspicious of the idea that we need to make the commit messages automated-tool-friendly. What tools are there that would need to extract this info, and would we trust them if they didn't understand "nuances"? I'm on board with Bruce's template as being a checklist of points to be sure to cover when composing a commit message. I'm not sure we need fixed-format rules. regards, tom lane
В списке pgsql-hackers по дате отправления: