Mercurial Mercurial > pub > hg > evolve / changeset
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | raw | zip | gz | bz2 | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
topic: dedent items about publishing behavior in docstring stable
authorDenis Laxalde <denis.laxalde@logilab.fr>
Wed, 23 May 2018 11:03:31 +0200
branchstable
changeset 3765 4aabc5c8b2af
parent 3764 f0f9139016d8
child 3766 6352dc395ebf
topic: dedent items about publishing behavior in docstring Also change item bullets from '#' to '*'.
hgext3rd/topic/__init__.py file | annotate | diff | comparison | revisions
tests/test-topic.t file | annotate | diff | comparison | revisions 
--- 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
--- a/tests/test-topic.t	Wed May 23 11:00:11 2018 +0200
+++ b/tests/test-topic.t	Wed May 23 11:03:31 2018 +0200
@@ -92,22 +92,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
evolve