Re: [COMMITTERS] pgsql: Also update ChangerLog file.
От | Magnus Hagander |
---|---|
Тема | Re: [COMMITTERS] pgsql: Also update ChangerLog file. |
Дата | |
Msg-id | 9837222c1001090902n3c3fc8a6yf071b93cf58fb6e0@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: Also update ChangerLog file. (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On Sat, Jan 9, 2010 at 17:55, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Michael Meskes <meskes@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. +1. Seems really weird (and unnecessary) to have a changelog for just one small "subsystem", when we don't have it for the others. -- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
В списке pgsql-hackers по дате отправления: