Mercurial > hg

changeset 9893:af873901b575 stable

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
commands, dates: use real lists instead of literal blocks
author Martin Geisler <mg@lazybytes.net>
date Thu, 19 Nov 2009 23:29:02 +0100
parents 4322e39bd525
children b755a886e8b7
files help/dates.txt mercurial/commands.py
diffstat 2 files changed, 28 insertions(+), 28 deletions(-) [+]
line wrap: on
line diff
--- a/help/dates.txt	Thu Nov 19 23:27:11 2009 +0100
+++ b/help/dates.txt	Thu Nov 19 23:29:02 2009 +0100
@@ -3,34 +3,34 @@
 - backout, commit, import, tag: Specify the commit date.
 - log, revert, update: Select revision(s) by date.
 
-Many date formats are valid. Here are some examples::
+Many date formats are valid. Here are some examples:
 
-  "Wed Dec 6 13:18:29 2006" (local timezone assumed)
-  "Dec 6 13:18 -0600" (year assumed, time offset provided)
-  "Dec 6 13:18 UTC" (UTC and GMT are aliases for +0000)
-  "Dec 6" (midnight)
-  "13:18" (today assumed)
-  "3:39" (3:39AM assumed)
-  "3:39pm" (15:39)
-  "2006-12-06 13:18:29" (ISO 8601 format)
-  "2006-12-6 13:18"
-  "2006-12-6"
-  "12-6"
-  "12/6"
-  "12/6/6" (Dec 6 2006)
+- ``Wed Dec 6 13:18:29 2006`` (local timezone assumed)
+- ``Dec 6 13:18 -0600`` (year assumed, time offset provided)
+- ``Dec 6 13:18 UTC`` (UTC and GMT are aliases for +0000)
+- ``Dec 6`` (midnight)
+- ``13:18`` (today assumed)
+- ``3:39`` (3:39AM assumed)
+- ``3:39pm`` (15:39)
+- ``2006-12-06 13:18:29`` (ISO 8601 format)
+- ``2006-12-6 13:18``
+- ``2006-12-6``
+- ``12-6``
+- ``12/6``
+- ``12/6/6`` (Dec 6 2006)
 
-Lastly, there is Mercurial's internal format::
+Lastly, there is Mercurial's internal format:
 
-  "1165432709 0" (Wed Dec 6 13:18:29 2006 UTC)
+- ``1165432709 0`` (Wed Dec 6 13:18:29 2006 UTC)
 
 This is the internal representation format for dates. unixtime is the
 number of seconds since the epoch (1970-01-01 00:00 UTC). offset is
 the offset of the local timezone, in seconds west of UTC (negative if
 the timezone is east of UTC).
 
-The log command also accepts date ranges::
+The log command also accepts date ranges:
 
-  "<{datetime}" - at or before a given date/time
-  ">{datetime}" - on or after a given date/time
-  "{datetime} to {datetime}" - a date range, inclusive
-  "-{days}" - within a given number of days of today
+- ``<{datetime}`` - at or before a given date/time
+- ``>{datetime}`` - on or after a given date/time
+- ``{datetime} to {datetime}`` - a date range, inclusive
+- ``-{days}`` - within a given number of days of today
--- a/mercurial/commands.py	Thu Nov 19 23:27:11 2009 +0100
+++ b/mercurial/commands.py	Thu Nov 19 23:29:02 2009 +0100
@@ -2740,13 +2740,13 @@
     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
+    and their effects can be rolled back:
+
+    - commit
+    - import
+    - pull
+    - push (with this repository as destination)
+    - unbundle
 
     This command is not intended for use on public repositories. Once
     changes are visible for pull by other users, rolling a transaction