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

Re: Fixing a broken GIT repo

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Nov 18, 2011, 12:54 UTC
Message-ID
<CAMP44s2N3WU_vzW9+7cRm+kvKGsoaMbhtuoX6yuNx58EixTkqw@mail.gmail.com>
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:
Show 7 quoted lines
> 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
Previous: Bart van den BurgNext: Johannes Sixt
Message 2 of 5 in “Fixing a broken GIT repo”
  1. Bart van den BurgNov 18, 2011
  2. Felipe ContrerasNov 18, 2011
  3. Johannes SixtNov 18, 2011
  4. Erik Faye-LundNov 21, 2011
  5. Johannes SixtNov 21, 2011

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.