From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, 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> |
Subject: | Re: Mail thread references in commits |
Date: | 2016-11-30 18:50:15 |
Message-ID: | CAM-w4HNY_h656VEAga88Sn0xHRPQNX23Nu455r+ySD4UFuopKg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 30 November 2016 at 16:19, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> https://www.postgresql.org/message-id/CAB7nPqTHyDYF-FO+fZvxRhz-7_hPTm4RodBcsy9-NoqHvEtc3w@mail.gmail.com
>
> I'll be interested to know if it breaks anyone's MUA. If it doesn't all we
> will be arguing about are aesthetics, and I'm a firm believer in function
> over form.
I can't say I feel especially strongly either way on this but just to
toss out a small thing that might make a small difference....
If you happen to know how your message-ids are generated then you
might be able to do something useful with them. For instance, you
could search all git commits for urls to messages you wrote -- for
instance any commit that has CAB7nPq is referencing a message written
by Michael Paquier.
On the other hand you could put something naughty in the message-id
forcing everyone else to use URLs with dirty words in them. Or with
words like "terrorist" in them. Or with some javascript/html injection
attack of some sort...
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-11-30 18:52:53 | Re: Re: [COMMITTERS] pgsql: Build HTML documentation using XSLT stylesheets by default |
Previous Message | Robert Haas | 2016-11-30 18:47:23 | Re: EvalPlanQual() doesn't follow LockTuple() pattern |