mercurial/commands.py

15743:6266b1b970a5

    - import
    - pull
    - push (with this repository as the destination)
    - unbundle

    It's possible to lose data with rollback: commit, update back to
    an older changeset, and then rollback. The update removes the
    changes you committed from the working directory, and rollback
    removes them from history. To avoid data loss, you must pass
    --force in this case.

    This command is not intended for use on public repositories. Once
    changes are visible for pull by other users, rolling a transaction
    back locally is ineffective (someone else may already have pulled
    the changes). Furthermore, a race is possible with readers of the

15744:5a20115e7397

    - import
    - pull
    - push (with this repository as the destination)
    - unbundle

    To avoid permanent data loss, rollback will refuse to rollback a
    commit transaction if it isn't checked out. Use --force to
    override this protection.

    This command is not intended for use on public repositories. Once
    changes are visible for pull by other users, rolling a transaction
    back locally is ineffective (someone else may already have pulled
    the changes). Furthermore, a race is possible with readers of the