From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Patch to git_changelog for release note creation |
Date: | 2011-03-15 14:22:24 |
Message-ID: | 201103151422.p2FEMOP20929@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I would like to apply the attached patch to git_changelog for use in
> > creating the major release notes. I specifically added these flags:
>
> > --author-after Show author after the commit
> > --master-only Show commits made exclusively to the master branch
> > --reverse-order Show commits in reverse date order
>
> Your implementation of --master-only seems really grotty. Can't you
> just add "origin/master" to the basic git log command?
I need commits that went exclusively to the master branch --- a commit
the goes to master and a subbranch should not appear because it was
already present in a minor release.
> As for --reverse-order, what's that got to do with preparing release
> notes? The end product shouldn't be particularly sensitive to the order
> of commit of features ...
Many commits reference earlier commits so having them in oldest-first
order makes the aggregation of those commits easier.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-03-15 14:25:22 | Re: new keywords in 9.1 |
Previous Message | Tom Lane | 2011-03-15 14:16:54 | Re: Macros for time magic values |