summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorspwhitton <spwhitton@web>2018-07-08 20:17:00 +0000
committeradmin <admin@branchable.com>2018-07-08 20:17:00 +0000
commit3431a9757a5654fce1e472073a5bf97aa515553f (patch)
tree554b7301fddac12df7eaedc42291b7a2486759d4
parent92f8c67aaddd24caade87433b75a279582cc6b8b (diff)
downloaddebug-me-3431a9757a5654fce1e472073a5bf97aa515553f.tar.gz
add link to simon tatham essay
-rw-r--r--doc/index.mdwn5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/index.mdwn b/doc/index.mdwn
index 16af569..7ea627d 100644
--- a/doc/index.mdwn
+++ b/doc/index.mdwn
@@ -16,7 +16,10 @@ Debugging a problem over email/irc/BTS is slow, tedious, and hard. The
developer needs to see the your problem to understand it. Debug-me aims to
make debugging fast, fun, and easy, by letting the developer access your
computer remotely, so they can immediately see and interact with the
-problem. Making your problem their problem gets it fixed fast.
+problem. Making your problem their problem gets it fixed fast. As
+Simon Tatham [[puts it|https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]],
+"In a nutshell, the aim of a bug report is to enable the programmer to see the
+program failing in front of them." debug-me does just that!
A debug-me session is logged and signed with the developer's GnuPG key,
producing a [[chain of evidence|evidence]] of what they saw and what they