On Sat, 31 Oct 2015 09:53:52 +0100 Stephan Beal <sgb...@googlemail.com> wrote:
> > Unless you delete .git your checkout is always in well defined > > state. > No, it's not. i once literally had one of the libgit maintainers at > my desk for a full hour trying to get my repo (of a project we were > both working on for our employers) back in a pushable state after it > got jumbled up by me copy/pasting commands suggested by StackOverflow > (about the worst place to get git advice). If one of the developers > takes that long to straighten it out, then something is (IMO) > fundamentally wrong. That's still barking at the wrong tree. You're unlikely to screw up a Fossil repo *that* much by mindlessly copying-and-pasting something from SO but that's because Fossil simply does not expose commands which allow you do perform intricate surgeries on your repo. To perform such fine operations, you have to be trained at them or just abstrain from doing them. Or at least try them in a sandbox first. It's like you being able to actually disassemble your car and them have a skilled technician assemble it back again because you have no idea how to do that. Sure, not everyone wants to be able to perform low-level operation on their repos, and not everyone wants to have the necessary skills. That's absolutely OK, but claiming that that not having tools to do that is somehow superior to another approach appears to be perfectly the same as fanboyism of those praising the products originating from a well-known company headquartered at Cupertino. :-) All-in-all, I'm afraid the thread got quickly derailed from the original problem: present DVCSs are known to suck at delivering simple and understandable concepts to "mere mortals". _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
