From: Joshua Berkus <josh@agliodbs.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Greg Smith <greg@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Last gasp
Date: Thu, 12 Apr 2012 10:12:52 -0500 (CDT)
Message-ID: <216417146.268570.1334243572925.JavaMail.root@mail-1.01.com> (raw)
In-Reply-To: <CABUevEwuCsNzxhfoq-gikcR6x35KUdipM9M8q0YpoVqyT3ixsA@mail.gmail.com>
> If we were actually using git branches for it, the CF app could
> automatically close entries when they were committed. But that
> requires them to be committed *unmodified*, and I'm not sure that's
> reasonable. I also think requiring a git branch for the *simple*
> changes is adding more tooling and not less, and thus fails on that
> suggestion.
Well actually, the other advantage of using branches is that it would encourage committers to bounce a patch back to the submitter for modification *instead of* doing it themselves. This would both have the advantage of saving time for the committer, and doing a better job of teaching submitters how to craft patches which don't need to be modified. Ultimately, we need to train new major contributors in order to get past the current bottleneck.
Of course, this doesn't work as well for contributors who *can't* improve their patches, such as folks who have a language barrier with the comments. But it's something to think about.
--Josh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: josh@agliodbs.com, magnus@hagander.net, robertmhaas@gmail.com, peter_e@gmx.net, greg@2ndquadrant.com, tgl@sss.pgh.pa.us
Subject: Re: Last gasp
In-Reply-To: <216417146.268570.1334243572925.JavaMail.root@mail-1.01.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox