From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add links to commit fests to patch summary page |
Date: | 2016-02-02 11:47:31 |
Message-ID: | CABUevEx5zQn9UcoUCzs8to9mWuTqtH0qoWgTMwArjus-GH4NYg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Feb 2, 2016 at 2:46 AM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> 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.
Just to be clear, you're looking for the ones that are for the non-current
one? Because you already have a link to the current commitfest in the
breadcrumbs at the top of the page. Or am I misunderstanding completely?
> (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*
>
But they're awesome when the developer is lazy! :) Patches welcome ;)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Kouhei Kaigai | 2016-02-02 11:53:50 | Re: Way to check whether a particular block is on the shared_buffer? |
Previous Message | Anastasia Lubennikova | 2016-02-02 11:47:29 | Re: [WIP] Effective storage of duplicates in B-tree index. |