| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Increase git_changelog's timestamp_slop from 10 min to 1 day. |
| Date: | 2013-12-02 16:33:57 |
| Message-ID: | E1VnWRZ-0007t5-AL@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Increase git_changelog's timestamp_slop from 10 min to 1 day.
Many committers seem to now be using a work flow in which back-patched
commits are timestamped minutes or even hours apart in different branches
(most likely because they commit in one branch before starting work on
the next one). git_changelog was failing to merge its reports in such
cases, so increase the max time it's willing to merge commits across.
I considered getting rid of the limit altogether, but that produces
some odd results in terms of how the merged commit gets sorted relative
to unrelated commits.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/7a1e34d3713c13b3b2c81f0410a6629362b37b00
Modified Files
--------------
src/tools/git_changelog | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-12-02 17:17:53 | pgsql: Improve draft release notes. |
| Previous Message | Robert Haas | 2013-12-02 16:19:44 | pgsql: Flag mmap implemenation of dynamic shared memory as resize-capab |