Skip to content

Commit ce1dcd4

Browse files
committed
Rename git_topo_order -> git_changelog, per discussion.
1 parent c8c03d7 commit ce1dcd4

File tree

2 files changed

+12
-6
lines changed

2 files changed

+12
-6
lines changed

src/tools/RELEASE_CHANGES

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ For All Releases (major, minor, beta, RC)
66
(by packager) (beta)
77

88
* Release notes
9-
o run git log and, if useful, src/tools/git_topo_order
9+
o run git log and, if useful, src/tools/git_changelog
1010
o update doc/src/sgml/release.sgml
1111
o run spellchecker on result
1212
o add SGML markup
@@ -31,7 +31,7 @@ For Major Releases
3131
(in addition to the above)
3232

3333
* Release notes
34-
o use git log or src/tools/git_topo_order to find the relevant commits
34+
o use git log or src/tools/git_changelog to find the relevant commits
3535
o check completion of items that have been marked as completed at
3636
http://wiki.postgresql.org/wiki/Todo
3737
o remove completed TODO items
@@ -76,7 +76,7 @@ Starting a New Development Cycle
7676
Creating Back-Branch Release Notes
7777
==================================
7878

79-
* Run src/tools/git_topo_order to generate a list of relevant commits
79+
* Run src/tools/git_changelog to generate a list of relevant commits
8080

8181
* On the git master branch, edit and create SGML markup for the most recent
8282
branch in that branch's release-N.N.sgml file

src/tools/git_topo_order renamed to src/tools/git_changelog

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
#!/usr/bin/perl
22

3+
#
4+
# src/tools/git_changelog
35
#
46
# Display all commits on active branches, merging together commits from
57
# different branches that occur close together in time and with identical
@@ -18,7 +20,7 @@
1820
# for the portion of the history we imported from CVS, we expect that they
1921
# will be.
2022
#
21-
# Even though we don't use timestamps to order commits, it is used to
23+
# Even though we don't use timestamps to order commits, they are used to
2224
# identify which commits happened at about the same time, for the purpose
2325
# of matching up commits from different branches.
2426
#
@@ -29,9 +31,13 @@ require Date::Calc;
2931
require Getopt::Long;
3032
require IPC::Open2;
3133

34+
# Adjust this list when the set of active branches changes.
3235
my @BRANCHES = qw(master REL9_0_STABLE REL8_4_STABLE REL8_3_STABLE
3336
REL8_2_STABLE REL8_1_STABLE REL8_0_STABLE REL7_4_STABLE);
3437

38+
# Might want to make this parameter user-settable.
39+
my $timestamp_slop = 600;
40+
3541
my $since;
3642
Getopt::Long::GetOptions('since=s' => \$since) || usage();
3743
usage() if @ARGV;
@@ -114,7 +120,7 @@ sub push_commit {
114120
my $ts = parse_datetime($c->{'date'});
115121
my $cc;
116122
for my $candidate (@{$all_commits{$ht}}) {
117-
if (abs($ts - $candidate->{'timestamp'}) < 600
123+
if (abs($ts - $candidate->{'timestamp'}) < $timestamp_slop
118124
&& !exists $candidate->{'branch_position'}{$c->{'branch'}})
119125
{
120126
$cc = $candidate;
@@ -149,7 +155,7 @@ sub parse_datetime {
149155

150156
sub usage {
151157
print STDERR <<EOM;
152-
Usage: git-topo-order [--since=SINCE]
158+
Usage: git_changelog [--since=SINCE]
153159
EOM
154160
exit 1;
155161
}

0 commit comments

Comments
 (0)