From: walt <wa1ter@myrealbox.com>
To: git@vger.kernel.org
Subject: 'bad file' error updating from Linus
Date: Thu, 22 Sep 2005 04:40:13 -0700 [thread overview]
Message-ID: <dgu56t$d2p$1@sea.gmane.org> (raw)
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
fatal: git-cat-file e98c07b9eabedfb1d7ebef61af475bdebe1dd64d: bad file
error: unable to find e98c07b9eabedfb1d7ebef61af475bdebe1dd64d
fatal: git-cat-file e98c07b9eabedfb1d7ebef61af475bdebe1dd64d: bad file
Invalid tree id: e98c07b9eabedfb1d7ebef61af475bdebe1dd64d
Is this a kernel.org rsync problem, perhaps?
(I'm running the latest releases of cogito and git from kernel.org.)
next reply other threads:[~2005-09-22 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 11:40 walt [this message]
2005-09-22 12:42 ` 'bad file' error updating from Linus porpen
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='dgu56t$d2p$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).