From: | Joshua Drake <jd(at)commandprompt(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Mail thread references in commits |
Date: | 2016-11-18 03:43:21 |
Message-ID: | CAJvJg-SjS_gOHJXyJuwk8m6AKguP_x67SC+Of8dDPGUqw8RLsw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Why not hash the URL? Something like:
Http://postgresopen.org/archive/743257890976432
Where the hash is derived from the message if?
On Nov 17, 2016 17:40, "Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com> wrote:
>
> Tom Lane wrote:
> > Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > > I love seeing references to email threads in commit messages. It would
> > > make them a lot friendlier though if a full http URL were included
> > > instead of just a Message-ID,
> >
> > I've intentionally not done that, because it does not seem very
> > future-proof. The message ids will hopefully be unique indefinitely far
> > into the future, but the location of our archives could move.
>
> It won't. We have far too many in the archives to risk breaking them.
> In fact, we (Magnus) went great lengths to implement a system so that
> old-style PHP links (of which we have a bunch in very old archives,
> including in commit messages) continue to work to this day. We're far
> too invested in the system now, because of how successful it has proved
> to be.
>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Khandekar | 2016-11-18 04:29:16 | Re: Parallel bitmap heap scan |
Previous Message | Etsuro Fujita | 2016-11-18 03:26:06 | Re: Push down more UPDATEs/DELETEs in postgres_fdw |