hgext3rd/topic/__init__.py
branchstable
changeset 3765 4aabc5c8b2af
parent 3764 f0f9139016d8
child 3768 482195001997
child 3820 c274f6a38c57
--- a/hgext3rd/topic/__init__.py	Wed May 23 11:00:11 2018 +0200
+++ b/hgext3rd/topic/__init__.py	Wed May 23 11:03:31 2018 +0200
@@ -82,22 +82,22 @@
 phase usually happens on push, but it is possible to update that behavior. The
 server needs to have specific config for this.
 
-    # everything pushed become public (the default)::
+* everything pushed become public (the default)::
 
-        [phase]
-        publish = yes
+    [phase]
+    publish = yes
 
-    # nothing push turned public::
+* nothing push turned public::
 
-        [phase]
-        publish = no
+    [phase]
+    publish = no
 
-    # topic branches are not published, changeset without topic are::
+* topic branches are not published, changeset without topic are::
 
-        [phase]
-        publish = no
-        [experimental]
-        topic.publish-bare-branch = yes
+    [phase]
+    publish = no
+    [experimental]
+    topic.publish-bare-branch = yes
 
 In addition, the topic extension adds a ``--publish`` flag on :hg:`push`. When
 used, the pushed revisions are published if the push succeeds. It also applies