https://bz.mercurial-scm.org/show_bug.cgi?id=6857
Bug ID: 6857
Summary: hg rollback randomly has no effect,
Product: Mercurial
Version: 6.5.3
Hardware: PC
OS: Linux
Status: UNCONFIRMED
Severity: bug
Priority: wish
Component: Mercurial
Assignee: bugzi...@mercurial-scm.org
Reporter: php4...@gmail.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---
Unfortunately I don't know how to reproduce this at will.
This just happened to me for no apparent reason.
I tried reproducing at will but couldn't.
What I did was:
- in a repository where there were no uncommitted changes, I made some changes
- I committed with 'hg commit -m "bla bla bla"' (note: i did NOT push)
- I made some more changes
- I ran the command: "hg rollback"
I got this strange output, which makes no sense whatsoever to me:
```
repository tip rolled back to revision 351 (undo push-response)
```
Normally when I do rollback I get this:
```
repository tip rolled back to revision 351 (undo commit)
```
After that, the repository was NOT rolled back. The last commit was still
there. hg status and hg diff would still show only changes I had made after the
last commit, as if I hadn't rolled back.
Basically, the rollback command had no effect whatsoever.
I tried running "hg rollback" again. This time I got the message:
```
no rollback information available
```
which would be expected if the rollback had had effect.
I could not roll back in any way, I had to keep the commit and move on.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
