Re: Mail thread references in commits - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Mail thread references in commits
Date
Msg-id 16a18db5-6980-1142-153d-37e1d3ad8ee2@2ndquadrant.com
Whole thread Raw
In response to Re: Mail thread references in commits  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Mail thread references in commits  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
On 11/27/16 8:37 AM, Magnus Hagander wrote:
> Ok, we now have it. https://postgr.es/m/messageid will redirect to that
> messageid in the main archives.

I like the idea of recording the location of the discussion, but I'm not
fond of the URL shortener.  Besides the general problem that URL
shortening looks ugly and fake, it fragments the way we address things.
Ideally, message IDs should tie together our main development tools:
email, commit fest app, web site, and commits.  If we use different
addresses in each of them, it will be confusing and harder to tie things
together.  For example, I would ideally like to just paste the thread
URL from the commit fest app into the commit message.  If I have to
manually shorten the URL, then that is error prone and less interesting
to do.  Also, the commit fest app links to a thread, not a message.
Another concern is how search engines will process this.

Do we know of an actual length limit that is useful to aim for?  If we
just make it just a bit shorter but it's still too long for a large
class of email readers, depending on the message ID format, then it's
not that useful.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Remove the comment on the countereffectiveness of large shared_buffers on Windows
Next
From: Amit Langote
Date:
Subject: Minor correction in alter_table.sgml