From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add links to commit fests to patch summary page |
Date: | 2016-02-02 01:46:02 |
Message-ID: | 56B00A5A.8010401@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/1/16 6:15 PM, Alvaro Herrera wrote:
> Jim Nasby wrote:
>> It would be nice if the patch summary page (ie, [1]) had links to the
>> relevant entry in that CF. The specific need I see is if you look up a patch
>> in the current CF and it's been moved to the next CF you have to manually go
>> to that CF and search for the patch.
>
> Agreed, I could use that. In the "status" row, each commitfest entry
> (the "2015-11" text) could be a link to that patch in that commitfest.
Yeah, what I was thinking.
> (You can actually construct the URL easily just by changing the
> commitfest ID, which is the first number in the URL; for example 2016-01
> is /8/).
*waits for someone to comment on how surrogate keys are bad*
;P
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Verite | 2016-02-02 01:51:18 | Re: [patch] Proposal for \crosstabview in psql |
Previous Message | David G. Johnston | 2016-02-02 01:42:19 | Re: "using previous checkpoint record at" maybe not the greatest idea? |