Tom Lane wrote:
> Michael Meskes 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
On Sat, Jan 09, 2010 at 11:55:00AM -0500, Tom Lane wrote:
> 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
On Sat, Jan 9, 2010 at 17:55, Tom Lane wrote:
> Michael Meskes 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?
>
Michael Meskes 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
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
Michael Meskes wrote:
Log Message:
---
Also update ChangerLog file.
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?
Stefan
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.or
