| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, David E(dot) Wheeler <david(at)kineticode(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Extensions, this time with a patch |
| Date: | 2010-10-22 20:12:10 |
| Message-ID: | 1287778239-sup-6513@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Robert Haas's message of vie oct 22 17:07:10 -0300 2010:
> On Fri, Oct 22, 2010 at 4:02 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
> > That said, I don't think there's any reason now to stop a committer from
> > renaming files (as long as this has been previously discussed and agreed
> > to, just like any other commit).
>
> Yeah - what is the feasibility of cleaning up the things where there
> are naming inconsistencies right now?
We're in Git-land now. Why should we worry unnecessarily about old
restrictions? It wasn't a policy, just a tool limitation.
Do you have concrete proposals? If so please start a new thread :-)
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-10-22 20:13:31 | Re: Integer input functions for date and timestamp |
| Previous Message | Robert Haas | 2010-10-22 20:07:10 | Re: Extensions, this time with a patch |