Magnus Hagander wrote:
> On Tue, Feb 2, 2016 at 4:43 PM, Alvaro Herrera
> wrote:
>
> > Magnus Hagander wrote:
> >
> > > So from https://commitfest.postgresql.org/9/353/, you'd want links to
> > > /8/353/, /7/353/, /6/353/?
> >
> > Right.
> I'm not entirely sure what I'd use that for myself, but
On 2/2/16 9:46 AM, Magnus Hagander wrote:
I'm not entirely sure what I'd use that for myself, but that's trivial
to implement. Thus, done and published.
FWIW, my use case was actually to go from
https://commitfest.postgresql.org/8/353/ to
https://commitfest.postgresql.org/9/353/, which I need
On 2/2/16 6:35 AM, Alvaro Herrera wrote:
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.
+1
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble?
On Tue, Feb 2, 2016 at 4:43 PM, Alvaro Herrera
wrote:
> Magnus Hagander wrote:
>
> > So from https://commitfest.postgresql.org/9/353/, you'd want links to
> > /8/353/, /7/353/, /6/353/?
>
> Right.
>
>
I'm not entirely sure what I'd use that for myself, but that's trivial to
implement. Thus, done
Magnus Hagander wrote:
> So from https://commitfest.postgresql.org/9/353/, you'd want links to
> /8/353/, /7/353/, /6/353/?
Right.
--
Álvaro Herrerahttp://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mail
On Tue, Feb 2, 2016 at 1:35 PM, Alvaro Herrera
wrote:
> Magnus Hagander wrote:
> > On Tue, Feb 2, 2016 at 2:46 AM, Jim Nasby
> 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
Magnus Hagander wrote:
> On Tue, Feb 2, 2016 at 2:46 AM, Jim Nasby 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 lo
On Tue, Feb 2, 2016 at 2:46 AM, Jim Nasby 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
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
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 co
10 matches
Mail list logo