Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • You seem to imply that this is a git error. Ok, could be. I still assumed I lacked proper git understanding, because I am not as smart as Linus ;-) Commented Feb 20, 2013 at 13:49
  • @towi: No, I'm not implying that this is a git error, nor am I implying the opposite. I'm not familiar with the git internals. But as a general rule of thumb, by moving around .git folders into other working areas, we're potentially violating assumptions of git. If this results in erratic behaviour we cannot blame git, we have to blame ourselves for playing tricks with git. git provides means to fix that, e.g. the reset --hard. It's just that that's not what we want. This is exactly the reason why the init/remote add way is recommended, and all is well. Commented Feb 20, 2013 at 15:01
  • @towi and Oliver P: While I understand you'd like your particular case of error be solved, sometimes it's just advised to go with the general recommendations - especially if they fit your use case perfectly. There's also no data loss. And the remote add way of doing things can still be applied to a messed up situation like the one described by Oliver P Commented Feb 20, 2013 at 15:04
  • 1
    A downvote without a comment does not help to improve this answer, nor the site as a whole. Whoever downvotes, please leave a comment so the issue can be resolved. Commented Jun 28, 2013 at 9:17