[Bug 4732] New: Ctrl+c during unshelve with pending changes can lose those changes permanently
mercurial-bugs at selenic.com
mercurial-bugs at selenic.com
Wed Jun 24 05:37:48 UTC 2015
http://bz.selenic.com/show_bug.cgi?id=4732
Priority: normal
Bug ID: 4732
CC: mercurial-devel at selenic.com
Assignee: bugzilla at selenic.com
Summary: Ctrl+c during unshelve with pending changes can lose
those changes permanently
Severity: bug
Classification: Unclassified
OS: Mac OS
Reporter: durham at fb.com
Hardware: PC
Status: UNCONFIRMED
Version: default branch
Component: shelve
Product: Mercurial
If you have pending changes in your working copy, then run 'hg unshelve' and
ctrl+c after the 'temporarily committing pending changes' message, but before
the 'rebase' finishes, the temporarily committed changes are lost forever (not
to mention your working copy is left on an unknown commit).
This is caused by unshelve using a single transaction to perform the commit and
the rebase. If the rebase is aborted, the temporary commit is also truncated.
This will be fixed by the rewrite that shelve is in desperate need of.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Mercurial-devel
mailing list