# HG changeset patch
# User Martin Geisler <mg@daimi.au.dk>
# Date 1238879710 -7200
# Node ID 5c61c75c2384a051921f3eeffc4793dd0301ca63
# Parent  7b813bdbd5d072285af45e15cb95b80fd29268fa
bookmarks: word-wrap help texts at 70 characters

diff -r 7b813bdbd5d0 -r 5c61c75c2384 hgext/bookmarks.py
--- a/hgext/bookmarks.py	Sat Apr 04 21:09:43 2009 +0200
+++ b/hgext/bookmarks.py	Sat Apr 04 23:15:10 2009 +0200
@@ -15,14 +15,15 @@
 It is possible to use bookmark names in every revision lookup (e.g. hg
 merge, hg update).
 
-The bookmark extension offers the possiblity to have a more git-like experience
-by adding the following configuration option to your .hgrc:
+The bookmark extension offers the possiblity to have a more git-like
+experience by adding the following configuration option to your .hgrc:
 
 [bookmarks]
 track.current = True
 
-This will cause bookmarks to track the bookmark that you are currently on, and
-just updates it. This is similar to git's approach of branching.
+This will cause bookmarks to track the bookmark that you are currently
+on, and just updates it. This is similar to git's approach of
+branching.
 '''
 
 from mercurial.i18n import _
@@ -115,8 +116,8 @@
 
     Bookmarks are pointers to certain commits that move when
     commiting. Bookmarks are local. They can be renamed, copied and
-    deleted. It is possible to use bookmark names in 'hg merge' and 'hg
-    update' to update to a given bookmark.
+    deleted. It is possible to use bookmark names in 'hg merge' and
+    'hg update' to update to a given bookmark.
 
     You can use 'hg bookmark NAME' to set a bookmark on the current
     tip with the given name. If you specify a revision using -r REV