tests/test-topic-tutorial.t
changeset 3060 f43a310c4338
parent 3027 b220e2f5ebd5
child 3075 8feb2cae7eae
--- a/tests/test-topic-tutorial.t	Fri Oct 13 10:01:38 2017 +0530
+++ b/tests/test-topic-tutorial.t	Fri Oct 13 10:18:52 2017 +0530
@@ -101,7 +101,7 @@
 changeset yet:
 
   $ hg topics
-   * food
+   * food (0 changesets)
 
   $ hg summary
   parent: 0:38da43f0a2ea tip
@@ -259,7 +259,7 @@
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
 
   $ hg topics
-     food
+     food (2 changesets)
 
 Note that ``default`` (name of the branch) now refers to the tipmost
 changeset of default without a topic:
@@ -336,7 +336,7 @@
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
 
   $ hg topics
-   * food
+   * food (2 changesets)
 
 Updating to any changeset that is part of a topic activates the topic
 regardless of how the revision was specified:
@@ -349,7 +349,7 @@
   1 files updated, 0 files merged, 0 files removed, 0 files unresolved
 
   $ hg topics
-   * food
+   * food (2 changesets)
 
 .. Server side activity:
 
@@ -575,7 +575,7 @@
 The topic information will disappear when we publish the changesets:
 
   $ hg topics
-   * food
+   * food (2 changesets)
 
   $ hg push
   pushing to $TESTTMP/server (glob)
@@ -588,7 +588,7 @@
   active topic 'food' is now empty
 
   $ hg topics
-   * food
+   * food (0 changesets)
 
 The topic still exists, and any new commit will be in the topic. But
 note that it is now devoid of any commit.
@@ -764,8 +764,8 @@
 We now have two topics:
 
   $ hg topics
-   * drinks
-     tools
+   * drinks (2 changesets)
+     tools  (3 changesets)
 
 The information displayed by ``hg stack`` adapts to the active topic: