aboutsummaryrefslogtreecommitdiffstats
path: root/doc/tutorial.txt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/tutorial.txt')
-rw-r--r--doc/tutorial.txt11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/tutorial.txt b/doc/tutorial.txt
index 592aef5..0da1de2 100644
--- a/doc/tutorial.txt
+++ b/doc/tutorial.txt
@@ -74,11 +74,11 @@ Initialization
--------------
You're happily coding in your Arch_ / Bazaar_ / Darcs_ / Git_ /
-Mercurial_ versioned project and you discover a bug. "Hmm, I'll need
-a simple way to track these things", you think. This is where BE
-comes in. One of the benefits of distributed versioning systems is
-the ease of repository creation, and BE follows this trend. Just
-type::
+Mercurial_ / Monotone_ versioned project and you discover a bug.
+"Hmm, I'll need a simple way to track these things", you think. This
+is where BE comes in. One of the benefits of distributed versioning
+systems is the ease of repository creation, and BE follows this trend.
+Just type::
$ be init
Using <VCS> for revision control.
@@ -98,6 +98,7 @@ if you call it from a directory besides your project's root.
.. _Darcs: http://darcs.net/
.. _Git: http://git-scm.com/
.. _Mercurial: http://mercurial.selenic.com/
+.. _Monotone: http://www.monotone.ca/
Inside the ``.be`` directory (among other things) there will be a long
UUID_ directory. This is your bug directory. The idea is that you