From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Template for commit messages |
Date: | 2016-02-01 12:18:32 |
Message-ID: | 20160201121832.GA72511@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund wrote:
> On 2016-02-01 12:56:21 +0100, Magnus Hagander wrote:
> > 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.
>
> Raw messageids have the big big advantage that you can get them locally
> in your mailreader, and you can dereference them locally... I type
> esc-X id:$id<enter> and 20ms later I have the whole thread open.
Yes, +1 on that.
> Maybe I just travel too much, but travel time is often long and
> uninterrupted and thus pretty nice to work on patches.
I don't travel as much as you or Magnus do (!) but I do offline work a
lot, so I appreciate full message-ids.
> I don't really see the problem, even with gmail style messageids
> Discussion: CABUevEz_UJA0ddrW7apjh3Nm4p0KghwOPm0WPW4Mh_gT2-nRJw(at)mail(dot)gmail(dot)com
> isn't that bad.
Yes, yes, I prefer to use the full URL because then a machine can tell
whether it's an email address and not a message-id, which is useful for
mangling addresses while at the same time not mangling message-ids. But
I'm not going to force that on anybody.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-02-01 12:23:38 | Re: Several problems in tab-completions for SET/RESET |
Previous Message | Fujii Masao | 2016-02-01 12:15:20 | Re: Several problems in tab-completions for SET/RESET |