Re: gitweb is no longer a real-time view

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <kgrittn(at)mail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>
Subject: Re: gitweb is no longer a real-time view
Date: 2013-03-04 14:56:55
Message-ID: 20130304145655.GJ3943@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On 2013-03-04 15:52:59 +0100, Magnus Hagander wrote:
> On Mon, Mar 4, 2013 at 1:50 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>
> > I think the most realistic way to resolve this is to push the current
> > anongit state to master and cherry-pick
> > bc61878682051678ade5f59da7bfd90ab72ce13b ontop it. That way only
> > committers need to deal with rebasing their branches and not everyone
> > else.
>
> I satarted looking at doing this, but this is backwards, right?

Yes. Sorry.

> Commit bc61878682051678ade5f59da7bfd90ab72ce13b exists on anongit, and
> only there.

> So what we need is to reset master HEAD to that of anongit, and then
> cherrypick 3bf3ab8c563699138be02f9dc305b7b77a724307,

Uhm, that is in both, isn't it?

> d63977eea3ab18fdec05e370b633d10b9fd20179 and
> 5db5974c692b0fc68e7608dd85a6b4e6173a0f28 on top of that, no?

Yes.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Alvaro Herrera 2013-03-04 14:58:42 Re: gitweb is no longer a real-time view
Previous Message Magnus Hagander 2013-03-04 14:52:59 Re: gitweb is no longer a real-time view