3 ms·
Eh...I find git is actually really bad for this type of thing. It's too in the way. Git is great for "I'm throwing all this out, but want to remember what I did
by XorNot 11y ago
Eh...I find git is actually really bad for this type of thing. It's too in the way. Git is great for "I'm throwing all this out, but want to remember what I did or some of the neat things in it".
But to fix an accident? That's what ~5-min ZFS snapshots are for.
- shabble 11y agoThat sounds like a pretty nifty feature - can you point at any docs about how that works/how to set it up? At university the lab systems had a networked home directory setup, and one of the greatest things was a '/yesterday/' link to your personal homedir, exactly as it was 1 day ago. I have no idea how they set it up, but something along these lines is plausible.
- simoncion 11y agoHow are ~5 minute ZFS snapshots significantly better than git log --patch to look at your history, combined with git checkout $COMMIT to get the code to perform any tests required? (Or, if you have a reliable automated test, git bisect start HEAD $KNOWN_GOOD_COMMIT -- && git bisect run $TEST will automatically find the error for you.) [0][1] And remember that the git checkpoint creation process is -at its most verbose- running git commit -m "C" [0] You can use points-in-time as commit references, like 'master@{30 minutes ago}' or 'HEAD@{2016-01-01}' [1] And even if you don't have a test, you can easily manually run the bisect machinery.