From: <porpen@gmail.com>
To: walt <wa1ter@myrealbox.com>
Cc: git@vger.kernel.org
Subject: Re: 'bad file' error updating from Linus
Date: Thu, 22 Sep 2005 08:42:23 -0400 [thread overview]
Message-ID: <509c8057050922054272b823fe@mail.gmail.com> (raw)
In-Reply-To: <dgu56t$d2p$1@sea.gmane.org>
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.
On a whim, I'll suggest we relax and go get some breakfast. ;-) and
try again a little later...
Cheers!
-P
On 9/22/05, walt <wa1ter@myrealbox.com> wrote:
> cg-update this morning is giving me this error:
>
> receiving file list ... done
> v2.6.14-rc2
>
> wrote 134 bytes read 1116 bytes 833.33 bytes/sec
> total size is 738 speedup is 0.59
> Tree change: 044a500e46742d39d22f1781cfb64ba93b463e39:e98c07b9eabedfb1d7ebef61af475bdebe1dd64d
> error: unable to find e98c07b9eabedfb1d7ebef61af475bdebe1dd64d
next prev parent reply other threads:[~2005-09-22 12:42 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 [this message]
2005-09-22 21:44 ` walt
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=509c8057050922054272b823fe@mail.gmail.com \
--to=porpen@gmail.com \
--cc=git@vger.kernel.org \
--cc=wa1ter@myrealbox.com \
/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).