Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UCX18-0005uS-Lo for pgsql-www@arkaria.postgresql.org; Mon, 04 Mar 2013 15:09:30 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UCX18-0002Hq-5D for pgsql-www@arkaria.postgresql.org; Mon, 04 Mar 2013 15:09:30 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UCX17-0002Hl-Hi for pgsql-www@postgresql.org; Mon, 04 Mar 2013 15:09:29 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UCX0y-0002Dm-OK for pgsql-www@postgresql.org; Mon, 04 Mar 2013 15:09:29 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id r24F9AG1005347; Mon, 4 Mar 2013 10:09:10 -0500 (EST) From: Tom Lane To: Andres Freund cc: Alvaro Herrera , Magnus Hagander , Kevin Grittner , Peter Eisentraut , PostgreSQL WWW , Stephen Frost Subject: Re: gitweb is no longer a real-time view In-reply-to: <20130304144609.GI3943@awork2.anarazel.de> References: <19759.1362357835@sss.pgh.pa.us> <20130304020324.GE16142@tamriel.snowman.net> <2480.1362363162@sss.pgh.pa.us> <20130304023335.GH16142@tamriel.snowman.net> <20130304125013.GB3943@awork2.anarazel.de> <20130304143349.GX9507@alvh.no-ip.org> <4725.1362408038@sss.pgh.pa.us> <20130304144609.GI3943@awork2.anarazel.de> Comments: In-reply-to Andres Freund message dated "Mon, 04 Mar 2013 15:46:09 +0100" Date: Mon, 04 Mar 2013 10:09:10 -0500 Message-ID: <5346.1362409750@sss.pgh.pa.us> X-Pg-Spam-Score: -2.5 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-www Precedence: bulk Sender: pgsql-www-owner@postgresql.org Andres Freund writes: > On 2013-03-04 09:40:38 -0500, Tom Lane wrote: >> FWIW, I noticed something about a "forced update" when I did a git pull >> after Kevin's commits. I failed to pay enough attention though. Now >> that I look, the xml fix is not in my local history either, and I don't >> know what bc61878682051678ade5f59da7bfd90ab72ce13b is because none of >> the recent commits have that hash according to my repo: > That is/was your map_sql_value_to_xml_value() commit which is now not in > the normal history anymore because kevin pushed a HEAD that didn't > include it. You should be able to see it with git show > bc61878682051678ade5f59da7bfd90ab72ce13b Ah, right, so it is still there but it's not in the chain leading to HEAD. So "forced update" really means "I moved HEAD in a non fast forward way"? regards, tom lane -- Sent via pgsql-www mailing list (pgsql-www@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www