From 03258b9e7fdb5a6bf2cac18c4cdbf53984fb8a5f Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Sun, 13 May 2018 13:28:52 +0200 Subject: dashboard/app: remove most details from email footer Exact details of syzbot communication change over time, so it's a bad idea to hardcode them in each email. Full details are also quite lengthy, so we can't express all of them in each email header. And providing partial info may be worse than just providing a link to full info. So remove most details from email footer, and just give links to documentation. Also clarify docs re when "syz fix" should/can be used. --- docs/syzbot.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'docs/syzbot.md') diff --git a/docs/syzbot.md b/docs/syzbot.md index aeed83197..ea679e8ce 100644 --- a/docs/syzbot.md +++ b/docs/syzbot.md @@ -28,11 +28,11 @@ emails. The commands are: ``` #syz fix: exact-commit-title ```` -It's enough that the commit is merged into any tree, in particular, -you don't need to wait for the commit to be merged into upstream tree. -`syzbot` only needs to know the title by which it will appear in tested trees. -In case of an error or a title change, you can override the commit simply -by sending another `#syz fix` command. +It's enough that the commit is merged into any tree or you are reasonably sure +about its final title, in particular, you don't need to wait for the commit to +be merged into upstream tree. `syzbot` only needs to know the title by which +it will appear in tested trees. In case of an error or a title change, you can +override the commit simply by sending another `#syz fix` command. - to mark the bug as a duplicate of another `syzbot` bug: ``` #syz dup: exact-subject-of-another-report -- cgit mrf-deployment