| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, David Zuelke <dz(at)heroku(dot)com> |
| Subject: | Re: Fix for OpenSSL error queue bug |
| Date: | 2016-04-28 03:04:42 |
| Message-ID: | 13310.1461812682@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Peter Geoghegan wrote:
>> I'm not sure if project policy around backpatching (that commit
>> messages and so on should match exactly) has anything to say about the
>> case where backpatching follows several weeks after commit to the
>> master branch.
> There is no value in providing exact message matches when the backpatch
> occurs even after one other commit in the master branch.
Actually, git_changelog can merge identically-messaged commits despite
intervening commits. It's set up to not merge commits more than 24 hours
apart, though. We could loosen that requirement but I'm afraid it would
make things confusing to merge far-apart commits.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | david | 2016-04-28 03:20:33 | Re: Shared memory and processes |
| Previous Message | Michael Paquier | 2016-04-28 02:18:49 | Re: Parallel build with MSVC |