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-n...@mail.gmail.com isn't that bad. Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers