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

Re: how to recover a repository

From
Ddavid@lang.hm <david@lang.hm>
Date
Dec 17, 2010, 20:20 UTC
Message-ID
<alpine.DEB.2.00.1012171218450.18272@asgard.lang.hm>
In-Reply-To
<20101217044530.GA8590@burratino>
On Thu, 16 Dec 2010, Jonathan Nieder wrote:
Show 15 quoted lines
> Hi David,
>
> david@lang.hm wrote:
>
>> I managed to do a 'rm *' in the .git directory (the usual sort of
>> fat-fingering when cleaning up after another mistake)
>>
>> the subdirectories are still there.
>
> I'd suggest:
>
> 1. Make a backup!
> 2. From the worktree (i.e. parent to the .git directory),
>    run "git init".
> 3. git update-ref HEAD refs/heads/(branch you were on)

I was on the default branch but if I do 'git update-ref HEAD refs/heads/master' I get an error 'not a valid SHA1'

.git/refs/heads is empty
.git/logs/HEAD looks like it shows all the commits in it properly
David Lang
Show 5 quoted lines
> 4. git reset;	# (alas, the old index file is gone)
> 5. git diff; gitk --all
>
> See gitrepository-layout(7) for details.
>
Previous: Jonathan NiederNext: Jeff King
Message 3 of 5 in “how to recover a repository”
  1. david@lang.hmDec 17, 2010
  2. Jonathan NiederDec 17, 2010
  3. david@lang.hmDec 17, 2010
  4. Jeff KingDec 17, 2010
  5. david@lang.hmDec 17, 2010

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.