From: Jon Smirl <jonsmirl@gmail.com>
To: git <git@vger.kernel.org>
Subject: Linus kernel tree corrupt?
Date: Fri, 8 Jul 2005 11:57:11 -0400 [thread overview]
Message-ID: <9e473391050708085756bd463e@mail.gmail.com> (raw)
What happened in this session...
[jonsmirl@jonsmirl linus]$ cg update
11:52:32 URL:http://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.g
it/refs/heads/master [41/41] -> "refs/heads/origin" [1]
progress: 34 objects, 102329 bytes
error: File 9cd17004869977026b473030ebb5b6fb71bfcebf
(http://www.kernel.org/pub/
scm/linux/kernel/git/torvalds/linux-2.6.git/objects/9c/d17004869977026b473030ebb
5b6fb71bfcebf) corrupt
Cannot obtain needed tree 9cd17004869977026b473030ebb5b6fb71bfcebf
while processing commit 0000000000000000000000000000000000000000.
cg-pull: objects pull failed
[jonsmirl@jonsmirl linus]$ cg update
11:53:26 URL:http://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.g
it/refs/heads/master [41/41] -> "refs/heads/origin" [1]
Up to date.
Applying changes...
Branch already fully merged.
[jonsmirl@jonsmirl linus]$ cg pull
11:53:33 URL:http://www.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.g
it/refs/heads/master [41/41] -> "refs/heads/origin" [1]
Up to date.
[jonsmirl@jonsmirl linus]$ cg diff
error: cannot read sha1_file for 9cd17004869977026b473030ebb5b6fb71bfcebf
fatal: unable to read tree object 7fd73e9f39bf6003cc3188a10426b62d8c47ab40
[jonsmirl@jonsmirl linus]$
--
Jon Smirl
jonsmirl@gmail.com
next reply other threads:[~2005-07-08 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 15:57 Jon Smirl [this message]
2005-07-08 17:06 ` Linus kernel tree corrupt? Tony Luck
2005-07-09 10:43 ` Russell King
2005-07-09 11:55 ` Petr Baudis
2005-07-09 18:03 ` H. Peter Anvin
2005-07-10 15:23 ` Petr Baudis
2005-07-10 20:35 ` H. Peter Anvin
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=9e473391050708085756bd463e@mail.gmail.com \
--to=jonsmirl@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.