Re: Template for commit messages
От | Magnus Hagander |
---|---|
Тема | Re: Template for commit messages |
Дата | |
Msg-id | CABUevEz_UJA0ddrW7apjh3Nm4p0KghwOPm0WPW4Mh_gT2-nRJw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Template for commit messages (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: Template for commit messages
|
Список | pgsql-hackers |
On Mon, Feb 1, 2016 at 12:53 PM, Michael Paquier <michael.paquier@gmail.com> wrote:
On Mon, Feb 1, 2016 at 8:36 PM, Andres Freund <andres@anarazel.de> wrote:
> I personally, and I realize that I'm likely alone on that, would really
> like to see references to relevant threads. A year after a commit or
> such it often starts to get hard to know which threads a commit was
> about. Often it's easy enough if it's about a single feature, but
> bugfixes often originate in threads that have no directly corresponding
> thread. And often the commit happens a while after there's been activity
> in a thread. I spent days searching what thread "per discussion" in
> commit messages refers to.
+1. Having to look at the archives to find to which discussion a
commit is attached is a pain. Last time this was suggested though
there were concerns regarding the 72-80 character limit per line in a
commit message.
Let's just assume that we can fix that part. As in, we can expose either an internal db id or a short hash or something, from the archives server. We could then have that visible/linkable directly on the archives page, and one could copy/paste that link into the commit message. That way we can avoid the long messageids.
В списке pgsql-hackers по дате отправления: