| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Gregory Stark <stark(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Lessons from commit fest |
| Date: | 2008-04-19 02:53:31 |
| Message-ID: | 200804190253.m3J2rVx05277@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom Lane wrote:
> >> If we're going to go down this path, why would we not put the
> >> "reference" typedef list into CVS?
>
> > Uh, I assume we don't want an automated system updating the file in CVS.
>
> Nowhere did I suggest that. What I suggested is that the "considered
> good" reference list should be in CVS, not on some random wiki page.
> In particular there's something pretty broken about the idea of a file
> in CVS telling people to go to a wiki page for important data.
I have no problem using a URL to pull down the typedef list via wget.
How is that CVS file going to be updated? Is someone manually going to
update it in CVS, and how often?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-04-19 03:01:09 | Re: Lessons from commit fest |
| Previous Message | Tom Lane | 2008-04-19 02:50:35 | Re: Lessons from commit fest |