diff options
| author | chee <chee@snoot.club> | 2021-05-21 09:52:11 +0000 |
|---|---|---|
| committer | Daniel Micay <danielmicay@gmail.com> | 2021-05-21 06:21:26 -0400 |
| commit | cfc727f89cb0db8bdddec0233a35e9f237a8b807 (patch) | |
| tree | a8deb3ec45887ecd10f3a8a14a7dcbcd092b7924 | |
| parent | 2cc7f95515a7fad851b5bab04bd65d9812cc9b67 (diff) | |
Make "the graphene os issue tracker" a link to the issue tracker
i found it difficult to find :)
| -rw-r--r-- | static/usage.html | 22 |
1 files changed, 12 insertions, 10 deletions
diff --git a/static/usage.html b/static/usage.html index 0600411d..1d07ed7d 100644 --- a/static/usage.html +++ b/static/usage.html @@ -451,16 +451,18 @@ application when it violates the rules.</p> <p>If you run into an application aborting, try to come up with a process for - reproducing the issue and then capture a bug report via the 'Take bug report' feature - in Developer options. Report an issue to the GrapheneOS OS issue tracker and email the - bug report capture zip to contact@grapheneos.org with the issue tracker number in the - subject like "Bug report capture for issue #104". The bug report capture includes - plain text 'tombstones' with logs, tracebacks, address space layout, register content - and a tiny bit of context from memory from areas that are interesting for debugging. - This may contain some sensitive data. Feel free to provide only the tombstone for the - relevant crash and filter out information you don't want to send. However, it will be - more difficult to debug if you provide less of the information. If the app doesn't - work with sensitive information, just send the whole tombstone.</p> + reproducing the issue and then capture a bug report via the 'Take bug report' + feature in Developer options. Report an issue to <a + href="https://github.com/GrapheneOS/os-issue-tracker/issues">the GrapheneOS OS + issue tracker</a> and email the bug report capture zip to contact@grapheneos.org + with the issue tracker number in the subject like "Bug report capture for issue + #104". The bug report capture includes plain text 'tombstones' with logs, + tracebacks, address space layout, register content and a tiny bit of context + from memory from areas that are interesting for debugging. This may contain + some sensitive data. Feel free to provide only the tombstone for the relevant + crash and filter out information you don't want to send. However, it will be + more difficult to debug if you provide less of the information. If the app + doesn't work with sensitive information, just send the whole tombstone.</p> </section> <section id="wifi-privacy"> |