<p dir="ltr">Why not hash the URL? Something like:<p dir="ltr"><a
href="Http://postgresopen.org/archive/743257890976432">Http://postgresopen.org/archive/743257890976432</a><p
dir="ltr">Wherethe hash is derived from the message if?<p dir="ltr">On Nov 17, 2016 17:40, "Alvaro Herrera" <<a
href="mailto:alvherre@2ndquadrant.com">alvherre@2ndquadrant.com</a>>wrote:<br /> ><br /> > Tom Lane wrote:<br
/>> > Andrew Dunstan <<a href="mailto:andrew@dunslane.net">andrew@dunslane.net</a>> writes:<br /> > >
>I love seeing references to email threads in commit messages. It would<br /> > > > make them a lot
friendlierthough if a full http URL were included<br /> > > > instead of just a Message-ID,<br /> > ><br
/>> > I've intentionally not done that, because it does not seem very<br /> > > future-proof. The message
idswill hopefully be unique indefinitely far<br /> > > into the future, but the location of our archives could
move.<br/> ><br /> > It won't. We have far too many in the archives to risk breaking them.<br /> > In fact,
we(Magnus) went great lengths to implement a system so that<br /> > old-style PHP links (of which we have a bunch in
veryold archives,<br /> > including in commit messages) continue to work to this day. We're far<br /> > too
investedin the system now, because of how successful it has proved<br /> > to be.<br /> ><br /> > --<br />
>Álvaro Herrera <a href="https://www.2ndQuadrant.com/">https://www.2ndQuadrant.com/</a><br /> >
PostgreSQLDevelopment, 24x7 Support, Remote DBA, Training & Services<br /> ><br /> ><br /> > --<br /> >
Sentvia pgsql-hackers mailing list (<a href="mailto:pgsql-hackers@postgresql.org">pgsql-hackers@postgresql.org</a>)<br
/>> To make changes to your subscription:<br /> > <a
href="http://www.postgresql.org/mailpref/pgsql-hackers">http://www.postgresql.org/mailpref/pgsql-hackers</a><br/>