Which is why I like my process. Redundancy is good. Not
dependent on some algorithm to piece things back together. Disks
are so frikkin large now that it is not an issue to have
multiple copies of the same file. If one set gets corrupted,
just use the one behind it. Fully self contained archived
snapshots not needing any program to access it.
------------
Scott Doctor
sc...@scottdoctor.com
------------------
On 10/31/2015 1:53 AM, Stephan Beal wrote:
On Sat, Oct 31, 2015 at 6:27 AM, Michal Suchanek
<hramr...@gmail.com <mailto:hramr...@gmail.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.
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed
byproduct of those who insist on a perfect world, freedom will
have to do." -- Bigby Wolf
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
