From d9a4a105a4a72c2cbc2aeb9ad438a0e09fab53fb Mon Sep 17 00:00:00 2001
From: zooko <>
Date: Thu, 12 Feb 2009 17:21:16 +0000
Subject: [PATCH] add link to BuildbotPolicy

[Imported from Trac: page Dev, version 67]
---
 Dev.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Dev.md b/Dev.md
index ba6da5f..bae021c 100644
--- a/Dev.md
+++ b/Dev.md
@@ -21,7 +21,7 @@ Views into the process of Tahoe hackery.
  * To fetch the source code using [darcs v2](http://darcs.net): `darcs get --lazy <http://allmydata.org/source/tahoe/trunk-hashedformat> tahoe`
   * `darcs v2` is highly recommended over `darcs v1`.  If you really don't want to install `darcs v2`, then you can use `darcs v1` instead, but you'll have to run a slightly different command-line and be prepared to wait for tens of minutes for the initial `get` to finish.  The command-line for `darcs v1` is: `darcs get <http://allmydata.org/source/tahoe/trunk-darcs1format> tahoe`.
  * <http://allmydata.org/source/tahoe/tarballs/> contains snapshots of current source code.
- * The Buildbot page (linked at the top of each page) shows current build and test results.
+ * The Buildbot page (linked at the top of each page) shows current build and test results.  See the [BuildbotPolicy](BuildbotPolicy) page.
  * The Timeline (linked at the top of each page) shows changes to the source code, the issue tickets, and the wiki (i.e. this web site).
  * [/../../tahoe-figleaf/current The code coverage statistics] show which lines of code get exercised by the unit tests.
    * [/../../tahoe-figleaf Archived data] is also available.