From: Felipe Contreras <felipe.contreras@gmail.com>
To: Bart van den Burg <bart@burgov.nl>
Cc: git@vger.kernel.org
Subject: Re: Fixing a broken GIT repo
Date: Fri, 18 Nov 2011 14:54:46 +0200 [thread overview]
Message-ID: <CAMP44s2N3WU_vzW9+7cRm+kvKGsoaMbhtuoX6yuNx58EixTkqw@mail.gmail.com> (raw)
In-Reply-To: <ja5dgo$nlf$1@dough.gmane.org>
On Fri, Nov 18, 2011 at 12:54 PM, Bart van den Burg <bart@burgov.nl> wrote:
> Needless to say, the mentioned object in fact does exist on the server:
> git@server:~/shifter_rai.git$ ls -la
> objects/85/d1ee957c65485ed9c937a4f1bfdd44fda4ea35
> -r--r--r-- 1 git git 153 Nov 18 11:39
> objects/85/d1ee957c65485ed9c937a4f1bfdd44fda4ea35
>
> Can anyone tell me what is happening here, and how I can fix it?
Well, if you can't find that object on the server or your local box,
then you would have to find the last commit that worked, and reset the
'master' branch to that.
--
Felipe Contreras
next prev parent reply other threads:[~2011-11-18 12:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 10:54 Fixing a broken GIT repo Bart van den Burg
2011-11-18 12:54 ` Felipe Contreras [this message]
2011-11-18 13:49 ` Johannes Sixt
2011-11-21 16:37 ` Erik Faye-Lund
2011-11-21 16:45 ` Johannes Sixt
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=CAMP44s2N3WU_vzW9+7cRm+kvKGsoaMbhtuoX6yuNx58EixTkqw@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=bart@burgov.nl \
--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).