Show More
@@ -4863,11 +4863,9 b' def rollback(ui, repo, **opts):' | |||
|
4863 | 4863 | - push (with this repository as the destination) |
|
4864 | 4864 | - unbundle |
|
4865 | 4865 | |
|
4866 | It's possible to lose data with rollback: commit, update back to | |
|
4867 | an older changeset, and then rollback. The update removes the | |
|
4868 | changes you committed from the working directory, and rollback | |
|
4869 | removes them from history. To avoid data loss, you must pass | |
|
4870 | --force in this case. | |
|
4866 | To avoid permanent data loss, rollback will refuse to rollback a | |
|
4867 | commit transaction if it isn't checked out. Use --force to | |
|
4868 | override this protection. | |
|
4871 | 4869 | |
|
4872 | 4870 | This command is not intended for use on public repositories. Once |
|
4873 | 4871 | changes are visible for pull by other users, rolling a transaction |
General Comments 0
You need to be logged in to leave comments.
Login now