3 ms·
> (*) both support something like stash but in hg it is easier to avoid that. Incidentally, using shelve in hg is the only way I've ever lost work in a VCS (I'
by nemetroid 8y ago
> (*) both support something like stash but in hg it is easier to avoid that.
Incidentally, using shelve in hg is the only way I've ever lost work in a VCS (I've made the same error in git as well, but a dropped stash can be found again).
> git log shows you history depending on the checked out version
> hg log shows you the whole history of the branch, also after your checked out version. Knowing where you are is very valuable.
git can show this, too, if you ask for it. If you've checked out some ancestor of `branch-name`, then `git log branch-name` will show `HEAD` next to the commit you've checked out. A single commit can belong to multiple branches, so if git showed you commits after your checked out version, which branch should it show? All of them?
> git - linus wants you to edit commits until they are perfect
You can use a never-rebase workflow in git as well, but most people elect not to.
- lixtra 8y ago> Incidentally, using shelve in hg is the only way I've ever lost work in a VCS (I've made the same error in git as well, but a dropped stash can be found again). At least today there is .hg/shelve-backup/