From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: kgdb tree fetch failure
Date: Thu, 23 Jul 2009 13:38:42 +1000 [thread overview]
Message-ID: <20090723133842.30ae062b.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4A67D36D.8070209@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 501 bytes --]
Hi Jason,
On Wed, 22 Jul 2009 22:05:17 -0500 Jason Wessel <jason.wessel@windriver.com> wrote:
>
> In the several years I have been using git, I have never seen it get
> corrupted until today.
Ouch!
> 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.
OK, thanks.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-07-23 3:38 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 [this message]
2009-07-23 3:48 ` Jason Wessel
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=20090723133842.30ae062b.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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).