changeset 2227:4f072bb06e89

deprecate undo command, replace with rollback command.
author Vadim Gelfer <vadim.gelfer@gmail.com>
date Mon, 08 May 2006 14:19:05 -0700
parents abfed2a82b07
children 8b106ff5b8a9
files mercurial/commands.py notes.txt tests/test-hook tests/test-rollback tests/test-rollback.out tests/test-undo tests/test-undo.out
diffstat 7 files changed, 72 insertions(+), 49 deletions(-) [+]
line wrap: on
line diff
--- a/mercurial/commands.py	Mon May 08 14:18:19 2006 -0700
+++ b/mercurial/commands.py	Mon May 08 14:19:05 2006 -0700
@@ -2232,7 +2232,7 @@
     return errs
 
 def revert(ui, repo, *pats, **opts):
-    """revert modified files or dirs to their states as of some revision
+    """revert files or dirs to their states as of some revision
 
     With no revision specified, revert the named files or directories
     to the contents they had in the parent of the working directory.
@@ -2361,6 +2361,35 @@
     repo.dirstate.update(remove[0], 'r')
     return r
 
+def rollback(ui, repo):
+    """roll back the last transaction in this repository
+
+    Roll back the last transaction in this repository, restoring the
+    project to its state prior to the transaction.
+
+    Transactions are used to encapsulate the effects of all commands
+    that create new changesets or propagate existing changesets into a
+    repository. For example, the following commands are transactional,
+    and their effects can be rolled back:
+
+      commit
+      import
+      pull
+      push (with this repository as destination)
+      unbundle
+
+    This command should be used with care. There is only one level of
+    rollback, and there is no way to undo a rollback.
+
+    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
+    repository; for example an in-progress pull from the repository
+    may fail if a rollback is performed.
+    """
+    repo.undo()
+
 def root(ui, repo):
     """print the root (top) of the current working dir
 
@@ -2676,19 +2705,12 @@
     return postincoming(ui, repo, modheads, opts['update'])
 
 def undo(ui, repo):
-    """undo the last commit or pull
-
-    Roll back the last pull or commit transaction on the
-    repository, restoring the project to its earlier state.
-
-    This command should be used with care. There is only one level of
-    undo and there is no redo.
-
-    This command is not intended for use on public repositories. Once
-    a change is visible for pull by other users, undoing it locally is
-    ineffective. Furthemore a race is possible with readers of the
-    repository, for example an ongoing pull from the repository will
-    fail and rollback.
+    """undo the last commit or pull (DEPRECATED)
+
+    (DEPRECATED)
+    This command is now deprecated and will be removed in a future
+    release. Please use the rollback command instead.  For usage
+    instructions, see the rollback command.
     """
     repo.undo()
 
@@ -3018,6 +3040,7 @@
           ('I', 'include', [], _('include names matching given patterns')),
           ('X', 'exclude', [], _('exclude names matching given patterns'))],
          _('hg revert [-r REV] [NAME]...')),
+    "rollback": (rollback, [], _('hg rollback')),
     "root": (root, [], _('hg root')),
     "^serve":
         (serve,
--- a/notes.txt	Mon May 08 14:18:19 2006 -0700
+++ b/notes.txt	Mon May 08 14:19:05 2006 -0700
@@ -121,7 +121,7 @@
 of each file touched and its length prior to the transaction. On
 abort, we simply truncate each file to its prior length. This is one
 of the nice properties of the append-only structure of the revlogs.
-We can also reuse this journal for "undo".
+We can also reuse this journal for "rollback".
 
 Merging between repositories:
 
--- a/tests/test-hook	Mon May 08 14:18:19 2006 -0700
+++ b/tests/test-hook	Mon May 08 14:19:05 2006 -0700
@@ -81,7 +81,7 @@
 echo 'preoutgoing = echo preoutgoing hook: s=$HG_SOURCE' >> ../a/.hg/hgrc
 echo 'outgoing = echo outgoing hook: n=$HG_NODE s=$HG_SOURCE' >> ../a/.hg/hgrc
 hg pull ../a
-hg undo
+hg rollback
 
 # preoutgoing hook can prevent outgoing changes
 echo 'preoutgoing.forbid = echo preoutgoing.forbid hook; exit 1' >> ../a/.hg/hgrc
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/tests/test-rollback	Mon May 08 14:19:05 2006 -0700
@@ -0,0 +1,15 @@
+#!/bin/sh
+
+mkdir t
+cd t
+hg init
+echo a > a
+hg add a
+hg commit -m "test" -d "1000000 0"
+hg verify
+hg parents
+hg status
+hg rollback
+hg verify
+hg parents
+hg status
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/tests/test-rollback.out	Mon May 08 14:19:05 2006 -0700
@@ -0,0 +1,18 @@
+checking changesets
+checking manifests
+crosschecking files in changesets and manifests
+checking files
+1 files, 1 changesets, 1 total revisions
+changeset:   0:0acdaf898367
+tag:         tip
+user:        test
+date:        Mon Jan 12 13:46:40 1970 +0000
+summary:     test
+
+rolling back last transaction
+checking changesets
+checking manifests
+crosschecking files in changesets and manifests
+checking files
+0 files, 0 changesets, 0 total revisions
+A a
--- a/tests/test-undo	Mon May 08 14:18:19 2006 -0700
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,15 +0,0 @@
-#!/bin/sh
-
-mkdir t
-cd t
-hg init
-echo a > a
-hg add a
-hg commit -m "test" -d "1000000 0"
-hg verify
-hg parents
-hg status
-hg undo
-hg verify
-hg parents
-hg status
--- a/tests/test-undo.out	Mon May 08 14:18:19 2006 -0700
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,18 +0,0 @@
-checking changesets
-checking manifests
-crosschecking files in changesets and manifests
-checking files
-1 files, 1 changesets, 1 total revisions
-changeset:   0:0acdaf898367
-tag:         tip
-user:        test
-date:        Mon Jan 12 13:46:40 1970 +0000
-summary:     test
-
-rolling back last transaction
-checking changesets
-checking manifests
-crosschecking files in changesets and manifests
-checking files
-0 files, 0 changesets, 0 total revisions
-A a