hgext/rebase.py
branchstable
changeset 10659 19c0ff5606e1
parent 10646 86dc21148bdb
child 10660 24555e216af6
child 10672 c2e1e637d4da
--- a/hgext/rebase.py	Mon Mar 08 03:07:35 2010 +0100
+++ b/hgext/rebase.py	Fri Mar 12 00:45:27 2010 +0100
@@ -38,17 +38,16 @@
     rebasing, but new changesets are added as its descendants.)
 
     You can specify which changesets to rebase in two ways: as a
-    \"source\" changeset or as a \"base\" changeset. Both are
-    shorthand for a topologically related set of changesets (the
-    \"source branch\"). If you specify source (``-s/--source``),
-    rebase will rebase that changeset and all of its descendants onto
-    dest. If you specify base (``-b/--base``), rebase will select
-    ancestors of base back to but not including the common ancestor
-    with dest. Thus, ``-b`` is less precise but more convenient than
-    ``-s``: you can specify any changeset in the source branch, and
-    rebase will select the whole branch. If you specify neither ``-s``
-    nor ``-b``, rebase uses the parent of the working directory as the
-    base.
+    "source" changeset or as a "base" changeset. Both are shorthand
+    for a topologically related set of changesets (the "source
+    branch"). If you specify source (``-s/--source``), rebase will
+    rebase that changeset and all of its descendants onto dest. If you
+    specify base (``-b/--base``), rebase will select ancestors of base
+    back to but not including the common ancestor with dest. Thus,
+    ``-b`` is less precise but more convenient than ``-s``: you can
+    specify any changeset in the source branch, and rebase will select
+    the whole branch. If you specify neither ``-s`` nor ``-b``, rebase
+    uses the parent of the working directory as the base.
 
     By default, rebase recreates the changesets in the source branch
     as descendants of dest and then destroys the originals. Use