From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Timezone matching script (win32) |
Date: | 2010-04-15 11:01:52 |
Message-ID: | p2k9837222c1004150401t300827c9z38e6d7c87a362b1f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 13, 2010 at 7:55 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>> Magnus Hagander wrote:
>>> This script should probably live in CVS, and be run when Microsoft
>>> releases new timezone data. Where should I put it - src/timezone or
>>> somewhere in src/tools? (it does read pgtz.c in the current directory,
>>> but it doesn't actually edit the file - just outputs on stdout a list
>>> of changes to be made to the file manually)
>
>> I think it should live in src/tools and be mentioned in
>> src/tools/RELEASE_CHANGES
>
> +1 for src/tools/, but the documentation note should probably be in
> src/timezone/README. This task isn't especially coupled to release
> times (at least not *our* release times). And it's definitely not
> likely to happen at the times anyone would be consulting
> RELEASE_CHANGES, because none of the release leadup work gets done
> on Windows machines.
I've applied the script with a small change to both the README and the
RELEASE_CHANGES files. Feel free to adjust that if you feel it's
wrong.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2010-04-15 13:08:54 | Re: Thoughts on pg_hba.conf rejection |
Previous Message | Magnus Hagander | 2010-04-15 08:12:15 | Re: Win32 timezone matching |