| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_migrator to /contrib in a later 9.0 beta |
| Date: | 2010-05-02 03:40:09 |
| Message-ID: | AANLkTimNHgymSX8itow6w1GTs2BNatLPhcu_l9-n-7qt@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, May 1, 2010 at 11:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> To the extent that future bug fixes are relevant to multiple versions
> of pg_migrator, we could just apply them to multiple branches, same as
> we manage such fixes for the core code. I don't see that trying to
> have a single version of pg_migrator is going to make things easier
> anywhere.
That might be OK if by "multiple versions" we mean "multiple branches
within the repository". But I'm not so sure about having a version in
the core repository and another version on pgfoundry, or something of
that sort.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-05-02 03:52:52 | Re: pg_migrator to /contrib in a later 9.0 beta |
| Previous Message | Tom Lane | 2010-05-02 03:38:06 | Re: pg_migrator to /contrib in a later 9.0 beta |