On 02/08/2016 01:11 PM, Peter Geoghegan wrote:
On Mon, Feb 8, 2016 at 12:18 PM, Robert Haas <robertmh...@gmail.com> wrote:
I accept that this might have been a somewhat isolated incident (that I couldn't easily get *at least* a little instant gratification), but it still should be avoided. You've accused me of burying the lead plenty of times. Don't tell me that it was too hard to prominently place those details somewhere where I or any other contributor could reasonably expect to find them, like the CF app page, or a wiki page that is maintained on an ongoing basis (and linked to at the start of each thread). If I said that that was too much to you, you'd probably shout at me. If I persisted, you wouldn't commit my patch, and for me that probably means it's DOA. I don't think I'm asking for much here. [1] http://www.postgresql.org/message-id/CAM3SWZSefE4uQk3r_3gwpfDWWtT3P51SceVsL4=g8v_me2a...@mail.gmail.com [2] http://www.postgresql.org/message-id/ca+tgmoarttf8eptbhinwxukfkctsfc7wtzfhgegqywe8e2v...@mail.gmail.com
This part of the thread seems like something that should be a new thread about how to write patches. I agree that patches that are large features that are in depth discussed on a maintained wiki page would be awesome. Creating that knowledge base without having to troll through code would be priceless in value.
Sincerely, JD -- Command Prompt, Inc. http://the.postgres.company/ +1-503-667-4564 PostgreSQL Centered full stack support, consulting and development. Everyone appreciates your honesty, until you are honest with them. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
