Re: Mail thread references in commits

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Joshua Drake <jd(at)commandprompt(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Mail thread references in commits
Date: 2016-11-19 15:16:34
Message-ID: 969a7d2c-7eff-f1b6-102e-fc255ad43a6e@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/19/2016 10:11 AM, Stephen Frost wrote:
> * Magnus Hagander (magnus(at)hagander(dot)net) wrote:
>> On Nov 19, 2016 15:33, "Andrew Dunstan" <andrew(at)dunslane(dot)net> wrote:
>>> I can think of at least one scenario where you might not easily have
>> access to any invented ID - you're the author and you have mailing list
>> me-too turned off, so you don't have anything that the mailing list has
>> inserted. I honestly think we should just stick with the Message-ID value
>> and get over the ugliness.
> That's actually not the case if we use a hash, because the client could
> figure out what the hash is before sending it.

The fact that it could possibly be done is not a good reason for doing
it. Every proposal along these lines strikes me as making more unobvious
hoops for people to jump through. We're just reinventing the wheel here
because we don't like the color of the standard wheels that some email
MUAs produce.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Karl O. Pinc 2016-11-19 15:22:20 Re: Patch to implement pg_current_logfile() function
Previous Message Stephen Frost 2016-11-19 15:11:37 Re: Mail thread references in commits