linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next:  kgdb tree fetch failure
Date: Wed, 22 Jul 2009 22:48:45 -0500	[thread overview]
Message-ID: <4A67DD9D.8030304@windriver.com> (raw)
In-Reply-To: <20090723133842.30ae062b.sfr@canb.auug.org.au>

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.

      reply	other threads:[~2009-07-23  3:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22 23:09 linux-next: kgdb tree fetch failure Stephen Rothwell
2009-07-23  3:05 ` Jason Wessel
2009-07-23  3:38   ` Stephen Rothwell
2009-07-23  3:48     ` Jason Wessel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A67DD9D.8030304@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).