Our team is just getting started with Mercurial. One of the first things we've started to play with is hg shelve
. Locally, I have no problem shelving changes. It all works perfectly from what I can tell. However, when I try to unshelve, I get the restoring backup files
message, but when I run hg diff
, there are no changes, and my changes are missing from the code. If i do hg unshelve -i
I can see the diff, but again, trying to unshelve seems to have no effect.
I've been trying to test it with some very simple changes that shouldn't be a problem in terms of conflicts, e.g. adding a test comment. I should note that I've tried hg unshelve -f
after which it says unshelve completed
but again, my changes are not restored.
Any ideas what I am doing wrong?
If it matters: Mercurial Distributed SCM (version 1.5.1+20100405)
hg shelve
isn't a part of mercurial, it's someone else's third-party extension. I suspect one reasonshelve
isn't part of mercurial is that it doesn't really fit the mercurial mindset. The mercurial way to shelve is to either just commit and then update to one revision back or to quickly clone your repo. A clone is instantaneous, takes up almost no space (hardlinks on modern filesystems), and doesn't have your uncommitted changes. Even if your team end up using shelve you should start them off with vanilla mercurial so they learn the idiom. – Talesman