From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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 17:16:02 |
Message-ID: | 20130304171601.GO3943@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On 2013-03-04 12:11:31 -0500, Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > On Mon, Mar 4, 2013 at 4:48 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
>
> 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?
git fsck --unreachable|grep "^unreachable commit" might do it.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2013-03-04 17:19:31 | Re: gitweb is no longer a real-time view |
Previous Message | Tom Lane | 2013-03-04 17:11:31 | Re: gitweb is no longer a real-time view |