On 31/10/15 06:27, Michal Suchanek wrote: [---] >> (For instance, my recent thread about how to clip off a a branch via the >> command line when the UI can’t do it because it was created empty, something >> Fossil can’t do, but which apparently CVS or SVN can, so it got into my >> Fossil tree when I converted.) >> >> This as compared to the sentiment in the XKCD comment, where if Git screws >> up, it’s often simpler to just toss the checkout and start over than try to >> recover. > > Seriously, how do you screw up like this with git? > > Unless you delete .git your checkout is always in well defined state.
No. I had a checkout of a repository which was working fine. One day I suddenly couldn't do things I have been doing all along with it (uncomplicated daily tasks; pull, commit, merge); git told me that my repository was broken. I googled for the error, found a stackexchange question about the error message and a few of the replies where along the line of "Yeah, that randomly happens sometimes, just type these commands and it'll fix it." (no explanation, just "the word on the street is that these commands help"). I copy-n-pasted the commands, git did some work on the repository and it fixed the problem (as far as I could tell). To your point though: Those who replied seemed to think this was normal, so I guess one could argue that error is a "well defined state". I was about to just delete my checkout and start again, but I was curious to see if anyone else had encountered it. -- Kind Regards, Jan _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
