Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UCX95-0006i9-Gp for pgsql-www@arkaria.postgresql.org; Mon, 04 Mar 2013 15:17:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UCX94-0003sr-Vs for pgsql-www@arkaria.postgresql.org; Mon, 04 Mar 2013 15:17:43 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UCX93-0003rn-M4 for pgsql-www@postgresql.org; Mon, 04 Mar 2013 15:17:41 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UCX91-0000Fd-Ry for pgsql-www@postgresql.org; Mon, 04 Mar 2013 15:17:41 +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 r24FHUPN005565; Mon, 4 Mar 2013 10:17:30 -0500 (EST) From: Tom Lane To: Alvaro Herrera cc: Andres Freund , Magnus Hagander , Kevin Grittner , Peter Eisentraut , PostgreSQL WWW , Stephen Frost Subject: Re: gitweb is no longer a real-time view In-reply-to: <20130304151127.GB9507@alvh.no-ip.org> References: <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> <20130304143852.GH3943@awork2.anarazel.de> <20130304145842.GZ9507@alvh.no-ip.org> <20130304150344.GK3943@awork2.anarazel.de> <20130304151127.GB9507@alvh.no-ip.org> Comments: In-reply-to Alvaro Herrera message dated "Mon, 04 Mar 2013 12:11:28 -0300" Date: Mon, 04 Mar 2013 10:17:30 -0500 Message-ID: <5564.1362410250@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 Alvaro Herrera writes: > I guess there clearly weren't enough protections in the gitmaster server > to prevent me from causing major breakage (hopefully there are now), Are there? I concur with your recommendation that we should lock this down *before* we set about repairing the master repo's contents. It seems particularly important that we do so if we're going to ask committers to rebase, because it seems like somebody who does that wrong could easily screw things up again. 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