From: Robin Rosenberg <robin.rosenberg@gmail.com>
To: John Bito <jwbito@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [EGIT] Push to GitHub caused corruption
Date: Tue, 11 Aug 2009 08:10:45 +0200 [thread overview]
Message-ID: <200908110810.45369.robin.rosenberg@gmail.com> (raw)
In-Reply-To: <3ae83b000908101446q2d4f1101we4bbd7023f78b03@mail.gmail.com>
måndag 10 augusti 2009 23:46:34 skrev John Bito <jwbito@gmail.com>:
> Using the 'release' build of EGit (0.4.9.200906240051) I pushed a
> commit to GitHub. After that, using git to pull, I get 'bad tree
> object' resulting in 'remote: aborting due to possible repository
> corruption on the remote side'. I had a similar problem back in April
> (using integration builds of 0.4.0). I'm willing to investigate if
> there's interest in finding the root of the problem.
Fixing problems related to repository integrity is definitely interesting. One
can live all kinds of problem, as long as they don't destroy anything.
-- robin
next prev parent reply other threads:[~2009-08-11 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 21:46 [EGIT] Push to GitHub caused corruption John Bito
2009-08-11 6:10 ` Robin Rosenberg [this message]
2009-08-11 22:52 ` John Bito
2009-08-14 9:19 ` Robin Rosenberg
2009-08-14 16:17 ` John Bito
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=200908110810.45369.robin.rosenberg@gmail.com \
--to=robin.rosenberg@gmail.com \
--cc=git@vger.kernel.org \
--cc=jwbito@gmail.com \
/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).