| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | 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:04:05 |
| Message-ID: | 20160201120405.GE8743@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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. 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 really see the problem, even with gmail style messageids
Discussion: CABUevEz_UJA0ddrW7apjh3Nm4p0KghwOPm0WPW4Mh_gT2-nRJw(at)mail(dot)gmail(dot)com
isn't that bad.
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vitaly Burovoy | 2016-02-01 12:07:51 | Re: Patch: make behavior of all versions of the "isinf" function be similar |
| Previous Message | Magnus Hagander | 2016-02-01 11:56:21 | Re: Template for commit messages |