2 ms·
I've found it distressingly easy to kill changesets in Git unintentionally. That does not make me a happy camper. I use Git because of Github - GH is a very
by pnathan 15y ago
I've found it distressingly easy to kill changesets in Git unintentionally.
That does not make me a happy camper. I use Git because of Github - GH is a very nice system. Hg IMO is a better interface if you just need to pick it up, hit it a few times, and then go do your thing.
- fr0sty 15y ago> I've found it distressingly easy to kill changesets in Git unintentionally. Mind if I ask how you manage to easily kill changesets in a 'distressingly easy' manner? In my experience it is somewhat difficult inadvertently lose commits (especially to lose them for good) unless you go out of your way to do so.
- pnathan 15y agoI like visualizing my graph tree in a GUI, so I grabbed GitX for Mac. I was trying to move my 'working directory' (hg term for the rev you're pointed at) to an earlier rev, so I used a 'hard reset of branch' option. Zoom. Away went my changesets, with me not having any idea how to scrape them up again. I think with enough google-fu I could have found them, but I had the files in my editor, so the issue was resolved. Another time came when I was trying to squash changesets, I managed to futz around with it to the point of absolutely killing a changeset. I don't know how I did that.