| From: | David Blewett <david(at)dawninglight(dot)net> |
|---|---|
| To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <gsstark(at)mit(dot)edu>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: branching for 9.2devel |
| Date: | 2011-05-04 01:51:46 |
| Message-ID: | BANLkTinStfkuJMYAaM-gX6PQ_5Nf_O0iKg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 2, 2011 at 2:01 AM, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> wrote:
> Can we not setup a automatic mechanism where a submitter can send a patch to
> some email id, the patch gets applied on the current HEAD, pgindent is run
> and the new patch is sent back to the submitter who can then submit it to
> the hackers for review. If the patch does not apply cleanly, the same can
> also be emailed back to the submitter.
This seems like a pretty good idea, but maybe it'd be easiest to take
it a step further and add an "automatic pgindent-ified" patch is
created when a patch is added to the commitfest app? If the original
patch didn't apply cleanly, just don't make the "pgindet-ified" link a
link and instead mark it red/strikethrough or some such?
It would probably be good to have both pieces, so that patch authors
could verify things outside of the app.
--
Thanks,
David Blewett
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Blewett | 2011-05-04 01:53:48 | Re: branching for 9.2devel |
| Previous Message | Ian Bailey-Leung | 2011-05-04 01:50:51 | Re: Unlogged vs. In-Memory |