From: Dmitry Potapov <dpotapov@gmail.com>
To: Tilo Schwarz <tilo@tilo-schwarz.de>
Cc: git@vger.kernel.org
Subject: Re: Problem: fatal oops during git fetch
Date: Thu, 14 Jan 2010 08:28:39 +0300 [thread overview]
Message-ID: <20100114052839.GG10586@dpotapov.dyndns.org> (raw)
In-Reply-To: <op.u6hrkho1a8ed4e@dellschleppa>
On Wed, Jan 13, 2010 at 11:03:43PM +0100, Tilo Schwarz wrote:
>
> Yesterday I tried to fetch bug fixes from one remote machine to the main
> development machine being on branch 'test' using
>
> git fetch remote/test
>
> I got something like
>
> fatal: oops 'SHA1'
> Fetch failed
>
> Any ideas what happened here?
My guess is that the remote repository is corrupted, and the specified SHA1
object was not found or it was corrupted. Try to run:
git fsck --full
in the remote repository.
Dmitry
prev parent reply other threads:[~2010-01-14 5:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 22:03 Problem: fatal oops during git fetch Tilo Schwarz
2010-01-14 5:28 ` Dmitry Potapov [this message]
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=20100114052839.GG10586@dpotapov.dyndns.org \
--to=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=tilo@tilo-schwarz.de \
/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).