# HG changeset patch
# User Martin Geisler <mg@lazybytes.net>
# Date 1247003682 -7200
# Node ID ec1cd317662539361b4e58cbf249a71785984bca
# Parent  59e5437bbcdc4b55e0c1492113828feed5e1fd6d
rebase: wrapped docstrings at 78 characters

diff -r 59e5437bbcdc -r ec1cd3176625 hgext/rebase.py
--- a/hgext/rebase.py	Tue Jul 07 23:54:42 2009 +0200
+++ b/hgext/rebase.py	Tue Jul 07 23:54:42 2009 +0200
@@ -7,8 +7,7 @@
 
 '''command to move sets of revisions to a different ancestor
 
-This extension lets you rebase changesets in an existing Mercurial
-repository.
+This extension lets you rebase changesets in an existing Mercurial repository.
 
 For more information:
 http://mercurial.selenic.com/wiki/RebaseProject
@@ -42,9 +41,9 @@
 def rebase(ui, repo, **opts):
     """move changeset (and descendants) to a different branch
 
-    Rebase uses repeated merging to graft changesets from one part of
-    history onto another. This can be useful for linearizing local
-    changes relative to a master development tree.
+    Rebase uses repeated merging to graft changesets from one part of history
+    onto another. This can be useful for linearizing local changes relative to
+    a master development tree.
 
     If a rebase is interrupted to manually resolve a merge, it can be
     continued with --continue/-c or aborted with --abort/-a.
diff -r 59e5437bbcdc -r ec1cd3176625 tests/test-rebase-parameters.out
--- a/tests/test-rebase-parameters.out	Tue Jul 07 23:54:42 2009 +0200
+++ b/tests/test-rebase-parameters.out	Tue Jul 07 23:54:42 2009 +0200
@@ -6,9 +6,9 @@
 
 move changeset (and descendants) to a different branch
 
-    Rebase uses repeated merging to graft changesets from one part of
-    history onto another. This can be useful for linearizing local
-    changes relative to a master development tree.
+    Rebase uses repeated merging to graft changesets from one part of history
+    onto another. This can be useful for linearizing local changes relative to
+    a master development tree.
 
     If a rebase is interrupted to manually resolve a merge, it can be
     continued with --continue/-c or aborted with --abort/-a.
@@ -34,9 +34,9 @@
 
 move changeset (and descendants) to a different branch
 
-    Rebase uses repeated merging to graft changesets from one part of
-    history onto another. This can be useful for linearizing local
-    changes relative to a master development tree.
+    Rebase uses repeated merging to graft changesets from one part of history
+    onto another. This can be useful for linearizing local changes relative to
+    a master development tree.
 
     If a rebase is interrupted to manually resolve a merge, it can be
     continued with --continue/-c or aborted with --abort/-a.
@@ -62,9 +62,9 @@
 
 move changeset (and descendants) to a different branch
 
-    Rebase uses repeated merging to graft changesets from one part of
-    history onto another. This can be useful for linearizing local
-    changes relative to a master development tree.
+    Rebase uses repeated merging to graft changesets from one part of history
+    onto another. This can be useful for linearizing local changes relative to
+    a master development tree.
 
     If a rebase is interrupted to manually resolve a merge, it can be
     continued with --continue/-c or aborted with --abort/-a.
@@ -90,9 +90,9 @@
 
 move changeset (and descendants) to a different branch
 
-    Rebase uses repeated merging to graft changesets from one part of
-    history onto another. This can be useful for linearizing local
-    changes relative to a master development tree.
+    Rebase uses repeated merging to graft changesets from one part of history
+    onto another. This can be useful for linearizing local changes relative to
+    a master development tree.
 
     If a rebase is interrupted to manually resolve a merge, it can be
     continued with --continue/-c or aborted with --abort/-a.