| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Michael Meskes <meskes(at)postgresql(dot)org> |
| Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Removed ecpg Changelog file that was only there for historical |
| Date: | 2010-01-12 16:01:58 |
| Message-ID: | 9837222c1001120801i4dc3890k106e4486c89b5d5b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Tue, Jan 12, 2010 at 15:22, Michael Meskes <meskes(at)postgresql(dot)org> wrote:
> On Tue, Jan 12, 2010 at 01:45:05PM +0100, Magnus Hagander wrote:
>> You probably want to do this on backbranches as well. Otherwise we're
>> going to have to maintain it in some branches and not in some (which
>> we *will* make mistakes if we try). And keeping it in there but not
>> maintaining it is even worse...
>
> TTBOMK the file has never been maintained in backbranched but always carried
> the release time status. I fail to see the advantage here.
Hmm, so we've basically been shipping out of date changelogs in
backbranches? That seems Bad (TM)..
Anyway, I vote for removing it there as well, but if you wan to keep
it, I don't care *that* much.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Bmomjian | 2010-01-12 18:06:24 | pg-migrator - pg_migrator: All building against any PG source >= 8.3. |
| Previous Message | Michael Meskes | 2010-01-12 14:22:50 | Re: pgsql: Removed ecpg Changelog file that was only there for historical |