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

Re: Repo corrupted somehow?

From
Andrew Arnott <andrewarnott@gmail.com>
Date
Nov 4, 2008, 15:12 UTC
Message-ID
<216e54900811040712k51db6fbfu44c59d9f90f1eabd@mail.gmail.com>
In-Reply-To
<216e54900811032334y35ada7daw753c0ad3073c0317@mail.gmail.com>

Nah, that wasn't a false alarm after all. It's happening again, only this time for dozens of files, and git rebase --abort git reset --hard

is not helping.
On Mon, Nov 3, 2008 at 11:34 PM, Andrew Arnott <andrewarnott@gmail.com> wrote:
Show 58 quoted lines
> I guess I was still in the middle of a rebase.  git rebase --abort
> sort of ultimately fixed it.
>
> On Mon, Nov 3, 2008 at 11:09 PM, Andrew Arnott <andrewarnott@gmail.com> wrote:
>> I was just git commit'ing, and then I was doing a git rebase to squash
>> several commits into one when the rebase failed.  I then did a
>> git checkout -f master
>> git reset --hard
>> but no matter what I do, git thinks that several files have changed.
>> The diff shows all the lines in these several files removed and then
>> added, yet without any changes made to them.  git reset --hard doesn't
>> revert the change. When I jump around history with git checkout these
>> files remain in their "changed" state.  I even tried "git clone" to
>> create a whole new repo, but one of these several files STILL
>> registered as changed before I made any changes.
>>
>> Any idea what's wrong and how to recover?
>>
>> Observe the below command buffer: (I can upload my repo so you can
>> clone it and perhaps repro it if you want).
>>
>> Andrew@LACKY /c/git/dotnetoauth
>> $ git status
>> # On branch master
>> # Changed but not updated:
>> #   (use "git add <file>..." to update what will be committed)
>> #
>> #       modified:   tools/Documentation.targets
>> #       modified:   tools/DotNetOpenAuth.Common.Settings.targets
>> #       modified:   tools/DotNetOpenAuth.Versioning.targets
>> #       modified:
>> tools/Sandcastle/Presentation/vs2005/Content/reference_content.xml
>> #       modified:   tools/libcheck.ps1
>> #       modified:   tools/sandcastle.targets
>> #
>> no changes added to commit (use "git add" and/or "git commit -a")
>>
>> Andrew@LACKY /c/git/dotnetoauth
>> $ git reset --hard
>> HEAD is now at 13d37b8 Patching up the bad merges in the phases.
>>
>> Andrew@LACKY /c/git/dotnetoauth
>> $ git status
>> # On branch master
>> # Changed but not updated:
>> #   (use "git add <file>..." to update what will be committed)
>> #
>> #       modified:   tools/Documentation.targets
>> #       modified:   tools/DotNetOpenAuth.Common.Settings.targets
>> #       modified:   tools/DotNetOpenAuth.Versioning.targets
>> #       modified:
>> tools/Sandcastle/Presentation/vs2005/Content/reference_content.xml
>> #       modified:   tools/libcheck.ps1
>> #       modified:   tools/sandcastle.targets
>> #
>> no changes added to commit (use "git add" and/or "git commit -a")
>>
>
Previous: Andrew ArnottNext: Jeff King
Message 3 of 9 in “Repo corrupted somehow?”
  1. Andrew ArnottNov 4, 2008
  2. Andrew ArnottNov 4, 2008
  3. Andrew ArnottNov 4, 2008
  4. Jeff KingNov 5, 2008
  5. Daniel BarkalowNov 5, 2008
  6. Andrew ArnottNov 5, 2008
  7. Daniel BarkalowNov 5, 2008
  8. Eyvind BernhardsenNov 5, 2008
  9. Andrew ArnottNov 8, 2008

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.