From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jason Wessel <jason.wessel@windriver.com>
Subject: Re: linux-next:  kgdb tree fetch failure
Date: Wed, 22 Jul 2009 22:48:45 -0500
Message-ID: <4A67DD9D.8030304@windriver.com>
References: <20090723090956.e6024af4.sfr@canb.auug.org.au><4A67D36D.8070209@windriver.com> <20090723133842.30ae062b.sfr@canb.auug.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <linux-next-owner@vger.kernel.org>
Received: from mail.windriver.com ([147.11.1.11]:36656 "EHLO mail.wrs.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752376AbZGWDsr (ORCPT <rfc822;linux-next@vger.kernel.org>);
	Wed, 22 Jul 2009 23:48:47 -0400
In-Reply-To: <20090723133842.30ae062b.sfr@canb.auug.org.au>
Sender: linux-next-owner@vger.kernel.org
List-ID: <linux-next.vger.kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org

Stephen Rothwell wrote:
> Hi Jason,
>
>   
>> My local git repository completely bailed, so I am going to reconstruct
>> the kgdb branches from a new clone.  There was no obvious way to recover
>> my archive. 
>>     
>
>   

As luck would have it, the pull of 2.6.31-rc4 magically fixed the local
archive, so kgdb-next branch is back in sync and updated.

Thanks,
Jason.