summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorJoey Hess <joeyh@joeyh.name>2017-05-20 17:38:07 -0400
committerJoey Hess <joeyh@joeyh.name>2017-05-20 17:38:07 -0400
commit62a38315781fc9dce7e2a8affea69df605ade248 (patch)
tree8b62ec4a16faf3d95df2b57b9748d7bdbeb9a27b
parent7b8a925a9c02b02e4af325f4ad210ae0be84938a (diff)
downloaddebug-me-62a38315781fc9dce7e2a8affea69df605ade248.tar.gz
add
-rw-r--r--doc/faq.mdwn6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/faq.mdwn b/doc/faq.mdwn
index 6884ec0..10d6422 100644
--- a/doc/faq.mdwn
+++ b/doc/faq.mdwn
@@ -62,6 +62,12 @@ For this to work, you have to have a copy of the session log file. This is
why the debug-me server will email it to you at the end of the session, to
make sure you get a copy.
+To verify a session log file, run: `debug-me --verify debug-me.log`
+That will display the gpg key of the developer who was active in
+that session, and verify the integrety of the log file.
+
+A debug-me log file can be replayed by running: `debug-me --reply debug-me.log`
+
### For Developers
#### What do I need to do to start using debug-me?