MIME-Version: 1.0
In-Reply-To: <9066.1362417091@sss.pgh.pa.us>
References: <20130304020324.GE16142@tamriel.snowman.net>
	<2480.1362363162@sss.pgh.pa.us>
	<20130304023335.GH16142@tamriel.snowman.net>
	<CABUevEwfw24iF9-czueLSmdFQwck012qfVmLXcoKbG37xG56jQ@mail.gmail.com>
	<CABUevEzM2F8qAxVds9Me-41L5BqeEGO4DuosCQhC0C6v05HPUw@mail.gmail.com>
	<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>
	<5564.1362410250@sss.pgh.pa.us>
	<CABUevEyh4tWHYTNcCFf_Pwm9WNBTz8ftcCh_1P=z3YiYn4J5jw@mail.gmail.com>
	<CABUevEzGmbk+EbpYDZjd+c+VsY2iqe0scntsS3bPuJYuC7OYnA@mail.gmail.com>
	<6927.1362412139@sss.pgh.pa.us>
	<CABUevEw-Ufchs-Pbebq4aJGMRn_XE4nXnPi8i95zdP+Uu_RzRA@mail.gmail.com>
	<9066.1362417091@sss.pgh.pa.us>
Date: Mon, 4 Mar 2013 18:19:31 +0100
Message-ID: 
 <CABUevEz-KOjzSbqkrtRhtXhKXU1eM_Gg8rkh0-WO1JqQn_QC=g@mail.gmail.com>
Subject: Re: gitweb is no longer a real-time view
From: Magnus Hagander <magnus@hagander.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
	Andres Freund <andres@2ndquadrant.com>,
	Kevin Grittner <kgrittn@mail.com>, Peter Eisentraut <peter_e@gmx.net>,
	PostgreSQL WWW <pgsql-www@postgresql.org>,
	Stephen Frost <sfrost@snowman.net>
Content-Type: text/plain; charset=ISO-8859-1
Precedence: bulk
Sender: pgsql-www-owner@postgresql.org

On Mon, Mar 4, 2013 at 6:11 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Magnus Hagander <magnus@hagander.net> writes:
>> On Mon, Mar 4, 2013 at 4:48 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Being a paranoid sort, I'm doing a full new "git clone" to compare
>>> to my old repo.  But assuming that that's okay, what instructions
>>> do you want to give committers about recovering?  There should be
>>> a followup with that info to the pgsql-hackers message you posted.
>
>> Yes, please do that comparison. Alvaro looked it over and found things
>> to look right, but one more paranoid check would be very good.
>
> AFAICT things are okay now.

Great. I'll "release" in the other thread then.


> One thing that would be interesting to try is to look for commits that
> are unreachable from any of the branch heads, to verify that we've
> not missed anything else.  I imagine git has a command for that, but
> I don't know it --- any ideas?

I'm running the fsck command suggested by Andres. It's taking a long
time to run, but I'll report if it finds something we shouldn't have.

-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


-- 
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www