[PATCH 3 of 5 topic-experiment] topics: some minute fixes to the documentation which shows up in help
Pulkit Goyal
7895pulkit at gmail.com
Sun Jun 18 18:12:22 EDT 2017
# HG changeset patch
# User Pulkit Goyal <7895pulkit at gmail.com>
# Date 1497820459 -19800
# Mon Jun 19 02:44:19 2017 +0530
# Node ID 46b090ecd2b9f69f52cae756008f199f78bb22c1
# Parent 3c6e013ffb8cb4e76b1e496bf8c34ebf790a506d
topics: some minute fixes to the documentation which shows up in help
I am not a native but these changes are simple and obvious.
diff --git a/hgext3rd/topic/__init__.py b/hgext3rd/topic/__init__.py
--- a/hgext3rd/topic/__init__.py
+++ b/hgext3rd/topic/__init__.py
@@ -10,7 +10,7 @@
Compared to bookmark, topic is reference carried by each changesets of the
series instead of just the single head revision. Topic are quite similar to
the way named branch work, except they eventualy fade away when the changeset
-becomes part of the immutable history. Changeset can below to both a topic and
+becomes part of the immutable history. Changeset can belong to both a topic and
a named branch, but as long as it is mutable, its topic identity will prevail.
As a result, default destination for 'update', 'merge', etc... will take topic
into account. When a topic is active these operations will only consider other
@@ -21,10 +21,11 @@
There is currently two commands to be used with that extension: 'topics' and
'stack'.
-The 'hg topics' command is used to set the current topic and list existing one.
-'hg topics --verbose' will list various information related to each topic.
+The 'hg topics' command is used to set the current topic, change and list
+existing one. 'hg topics --verbose' will list various information related to
+each topic.
-The 'stack' will show you in formation about the stack of commit belonging to
+The 'stack' will show you information about the stack of commit belonging to
your current topic.
Topic is offering you aliases reference to changeset in your current topic
More information about the Mercurial-devel
mailing list