From: "John M. Dlugosz" <ngnr63q02@sneakemail.com>
To: git@vger.kernel.org
Subject: Re: What's going on here? Bad repo, no error locally?
Date: Tue, 21 Apr 2009 23:37:05 -0500 [thread overview]
Message-ID: <gsm6tr$or7$1@ger.gmane.org> (raw)
In-Reply-To: <3e8340490904212121q4bf2e25dsf5673bff764895c9@mail.gmail.com>
Bryan Donlan wrote:
> Extract the object on developer B's workstation:
> git cat-file blob <object ID> > blob.dat
>
> Copy it to upstream, then do:
> git hash-object -w blob.dat
>
> If all goes well, hash-object will give you back the blob's ID, and
> the repository will fsck cleanly again.
Thanks, I was looking through the manual for that but wasn't sure how to put it together.
But, what could be wrong with B's repo that makes this happen repetetly? I assumed it was
network SNAFU, but after restoring the upstream repo, his push did it again.
--John
next prev parent reply other threads:[~2009-04-22 4:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 0:18 What's going on here? Bad repo, no error locally? John Dlugosz
2009-04-22 4:21 ` Bryan Donlan
2009-04-22 4:37 ` John M. Dlugosz [this message]
2009-04-22 4:52 ` Bryan Donlan
2009-04-22 5:06 ` Junio C Hamano
2009-04-22 15:59 ` John Dlugosz
2009-04-22 16:30 ` Brandon Casey
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='gsm6tr$or7$1@ger.gmane.org' \
--to=ngnr63q02@sneakemail.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).