-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
> How would this go with PostgreSQL? You can use the bug form on the web > site, but you can't attach any code, so the bug will just linger and > ultimately put more burden on a core contributor to deal with the > minutiae of developing, testing, and committing a trivial fix and > sending feedback to the submitter. Well, they could attach a link to a github patch... > Or the user could take the high road and develop and patch and submit it. > Just make sure it's in context diff format! Search the wiki if you don't > know how to do that! Send it to -hackers, your email will be held for > moderation. We won't actually do anything with your patch, but we will > tell you to add it to that commitfest app over there. You need to sign up > for an account to use that. We will deal with your patch in one or two > months. > But only if you review another patch. And you should sign up for that > other mailing list, to make sure you're doing it right. Chances are, the > first review you're going to get is that your patch doesn't apply anymore, > but which time you will have lost interest in the patch anyway. +1 to all that. Especially the signing up for the commitfest app. > Of course, Gerrit doesn't actually address most of the issues above, but > it could be part of a step forward. More of a step sideways. It doesn't address the bigger problems. - -- Greg Sabino Mullane g...@turnstep.com PGP Key: 0x14964AC8 201302081124 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAlEVJrkACgkQvJuQZxSWSshh3gCgz+XHwAbk5rryttYPi68j4EJi 7DcAnjEdxDD4Rm2/oDBaqHbOzQLwR6zR =0lnp -----END PGP SIGNATURE----- 2~ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
