# HG changeset patch
# User Chuck Tuffli <chuck@tuffli.net>
# Date 1613164561 28800
# Node ID aad3ee70a0bbc4727d10bed661eebf73090f1bc6
# Parent  c23cbde54a589ec4f6b6edd67bca5c150beea22f
doc: document stack as a substitue for MQ's qseries

diff -r c23cbde54a58 -r aad3ee70a0bb CHANGELOG
--- a/CHANGELOG	Wed Feb 03 08:07:10 2021 -0800
+++ b/CHANGELOG	Fri Feb 12 13:16:01 2021 -0800
@@ -1,6 +1,11 @@
 Changelog
 =========
 
+10.2.1 - in progress
+--------------------
+
+ * doc: document stack as a substitue for MQ's qseries
+
 10.2.0.post1 -- 2021-02-01
 --------------------------
 
diff -r c23cbde54a58 -r aad3ee70a0bb docs/from-mq.rst
--- a/docs/from-mq.rst	Wed Feb 03 08:07:10 2021 -0800
+++ b/docs/from-mq.rst	Fri Feb 12 13:16:01 2021 -0800
@@ -48,6 +48,27 @@
   [alias]
   wip = log -r 'not public()' --template='{rev}:{node|short} {desc|firstline}\n'
 
+Using the topic extension provides another way of looking at your
+work in progress. Topic branches are lightweight branches which
+disappear when changes are finalized. Although the underlying
+mechanics are different, both queues and topics help users
+organize and share their unfinished work. The topic extension
+provides the ``stack`` command. Similar to ``qseries``, ``stack``
+lists all changesets in a topic as well as other related
+information.
+
+.. code-block:: console
+
+  $ hg stack
+
+Installing the evolve extension also installs the topic extension. To enable
+it, add the following to your `hgrc` config:
+
+.. code-block:: ini
+
+  [extensions]
+  topic =
+
 hg qnew
 ```````