Magnus Hagander wrote:
> On Tue, Feb 2, 2016 at 2:46 AM, Jim Nasby <Jim.Nasby@bluetreble.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?
I think you are, because yes I don't care to go to the current
commitfest (I know how to do that) -- but I don't want to the toplevel
page for the other commitfest either: what I want is the link to go to
*that patch's* page in the other commitfest. That's also what I
think Jim wants.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services