From f8d92b9de46d57e2770d2afd3741a732ba1a01bc Mon Sep 17 00:00:00 2001 From: inferno-chromium Date: Sat, 26 Nov 2016 18:22:14 -0800 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a339245eb..aef8a0a5a 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,7 @@ and [integrates](docs/ideal_integration.md) them with the project's build and te ([Why different tracker?](docs/faq.md#why-do-you-use-a-different-issue-tracker-for-reportig-bugs-in-fuzz-targets)). Project owners are CC-ed to the bug report. - The bug is fixed upstream. -- [ClusterFuzz](docs/clusterfuzz.md) automatically verifies the fix, adds a comment and closes the issue. +- [ClusterFuzz](docs/clusterfuzz.md) automatically verifies the fix, adds a comment and closes the issue ([example](https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=53#c3)). - 7 days after the fix is verified or after 90 days after reporting, the issue becomes *public* ([guidelines](#bug-disclosure-guidelines)).