Re: Patch to git_changelog for release note creation

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch to git_changelog for release note creation
Date: 2011-03-15 14:33:23
Message-ID: 201103151433.p2FEXN922083@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
> Bottom line: I need to start the release notes today --- I can hack my
> own version and we can revisit this later, which I am afraid will be in
> one year, or we can just add what I have and we can keep hacking on it
> as needed.

Oh, one more thing. pgcvslog was added to src/tools by me for release
note generation. I asked for git_changelog for release note generation.
Now saying we don't want to modify git_changelog because it would be too
tied to release note generation seems silly because no one wanted the
tool until I added a CVS version for release notes. As proof, pgcvslog
output exactly the format I needed for release notes, and had no option
for any other output format.

As I understand it now, git_changelog is replacing pgcvslog and cvs2cl.

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

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2011-03-15 14:36:15 Re: Macros for time magic values
Previous Message Bruce Momjian 2011-03-15 14:25:35 Re: Patch to git_changelog for release note creation