| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Michael Meskes <meskes(at)postgresql(dot)org>, 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 14:22:50 |
| Message-ID: | 20100112142250.GB11058@feivel.credativ.lan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
ICQ: 179140304, AIM/Yahoo/Skype: michaelmeskes, Jabber: meskes(at)jabber(dot)org
VfL Borussia! Forca Barca! Go SF 49ers! Use: Debian GNU/Linux, PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-01-12 16:01:58 | Re: pgsql: Removed ecpg Changelog file that was only there for historical |
| Previous Message | Magnus Hagander | 2010-01-12 12:45:05 | Re: pgsql: Removed ecpg Changelog file that was only there for historical |