git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: walt <wa1ter@myrealbox.com>
To: git@vger.kernel.org
Subject: Re: 'bad file' error updating from Linus
Date: Thu, 22 Sep 2005 14:44:34 -0700	[thread overview]
Message-ID: <dgv8jv$amv$1@sea.gmane.org> (raw)
In-Reply-To: <509c8057050922054272b823fe@mail.gmail.com>

porpen@gmail.com wrote:
> You aren't alone.  I had a look at http://www.kernel.org/git/  only to
> find that the 2.6 kernel has been taken off the list...  /me thinks
> Linus is pushing an update as I type...

I think it was a disk failure, but no matter -- it's fixed now.

For the benefit of future googlers with the same 'bad file' error:

After I repeated the cg-update (successfully) I was still left with
the 'bad file' error.  I tried 'cg-restore' and the error went away.
Very nifty!

  reply	other threads:[~2005-09-22 21:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22 11:40 'bad file' error updating from Linus walt
2005-09-22 12:42 ` porpen
2005-09-22 21:44   ` walt [this message]
2005-09-22 23:32     ` Linus Torvalds
2005-09-23 19:43       ` H. Peter Anvin
2005-09-23  0:56     ` walt

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='dgv8jv$amv$1@sea.gmane.org' \
    --to=wa1ter@myrealbox.com \
    --cc=git@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).