Prev: dbt2-shell script problem
Next: 8.5alpha3 bug in information_schema.table_privileges
From: Bruce Momjian on 11 Jan 2010 20:18
Tom Lane wrote:
> Michael Meskes <meskes(a)postgresql.org> writes:
> > On Fri, Jan 08, 2010 at 03:41:10PM +0100, Stefan Kaltenbrunner wrote:
> >> Hmm not sure I find that commit message really helpful - but is it
> >> actually of any use to maintain a Changelog file specifically for
> >> ECPG?
>
> > Makes it easier to see what's new in ecpg when doing a new
> > release. But I guess we could get all this from the cvs log too. The
> > file has been there for a long time.
>
> Well, I'm pretty sure that release notes are prepared off of the cvs log
> entries. I've never looked at ecpg's Changelog when working on notes,
> and I'd be prepared to bet that Bruce hasn't either. My advice is to
> drop the Changelog file and be sure you describe changes appropriately
> in the commit messages.

Agreed. I was never aware of an ecpg changelog file. Let's remove it
and Michael can make any clarifications to the major releases he wants.

--
Bruce Momjian <bruce(a)momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: dbt2-shell script problem
Next: 8.5alpha3 bug in information_schema.table_privileges