Skip site navigation (1) Skip section navigation (2)

pgsql: Still more tweaking of git_changelog.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Still more tweaking of git_changelog.
Date: 2010-09-26 05:51:32
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committerspgsql-hackers
Still more tweaking of git_changelog.

1. Don't assume there's only one candidate match; check them all and use the
one with the closest timestamp.  Avoids funny output when someone makes
several successive commits with the same log message, as certain people
have been known to do.

2. When the same commit (with the same SHA1) is reachable from multiple
branch tips, don't report it for all the branches; instead report it only
for the first such branch.  Given our development practices, this case
arises only for commits that occurred before a given branch split off from
master.  The original coding blamed old commits on *all* the branches,
which isn't terribly useful; the new coding blames such a commit only on



Modified Files
src/tools/git_changelog |   24 +++++++++++++++++++-----
1 files changed, 19 insertions(+), 5 deletions(-)


pgsql-hackers by date

Next:From: Massa, Harald ArminDate: 2010-09-26 09:42:11
Subject: documentation udpates to pgupgrade.html
Previous:From: Itagaki TakahiroDate: 2010-09-26 04:35:41
Subject: Re: Help with User-defined function in PostgreSQL with Visual C++

pgsql-committers by date

Next:From: Andres FreundDate: 2010-09-26 10:36:47
Subject: Re: pgsql: Fix another join removal bug: the check on PlaceHolderVars was w
Previous:From: Tom LaneDate: 2010-09-26 04:22:58
Subject: pgsql: Fix some more bugs in git_changelog.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group