git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [EGIT] Push to GitHub caused corruption

From
RRRobin Rosenberg <robin.rosenberg@gmail.com>
Date
Aug 11, 2009, 06:10 UTC
Message-ID
<200908110810.45369.robin.rosenberg@gmail.com>
In-Reply-To
<3ae83b000908101446q2d4f1101we4bbd7023f78b03@mail.gmail.com>
måndag 10 augusti 2009 23:46:34 skrev John Bito <jwbito@gmail.com>:
Show 6 quoted lines
> 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
Previous: John BitoNext: John Bito
Message 2 of 5 in “[EGIT] Push to GitHub caused corruption”
  1. John BitoAug 10, 2009
  2. Robin RosenbergAug 11, 2009
  3. John BitoAug 11, 2009
  4. Robin RosenbergAug 14, 2009
  5. John BitoAug 14, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.