diff options
| author | Dave Rodgman <dave.rodgman@arm.com> | 2022-03-31 16:07:01 +0300 |
|---|---|---|
| committer | Dave Rodgman <dave.rodgman@arm.com> | 2022-03-31 16:43:16 +0300 |
| commit | 017a19997aa5b9298b5f748169461acbb1310018 (patch) | |
| tree | 0dbe3559757cc5a31e7be83c87f37334650b8467 /BUGS.md | |
| parent | a980adf4ce9f9d7b01f894e822902c1c70f146c6 (diff) | |
Update references to old Github organisation
Replace references to ARMmbed organisation with the new
org, Mbed-TLS, following project migration.
Signed-off-by: Dave Rodgman <dave.rodgman@arm.com>
Diffstat (limited to 'BUGS.md')
| -rw-r--r-- | BUGS.md | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -1,6 +1,6 @@ ## Known issues -Known issues in Mbed TLS are [tracked on GitHub](https://github.com/ARMmbed/mbedtls/issues). +Known issues in Mbed TLS are [tracked on GitHub](https://github.com/Mbed-TLS/mbedtls/issues). ## Reporting a bug @@ -9,12 +9,12 @@ If you think you've found a bug in Mbed TLS, please follow these steps: 1. Make sure you're using the latest version of a [maintained branch](BRANCHES.md): `master`, `development`, or a long-time support branch. -2. Check [GitHub](https://github.com/ARMmbed/mbedtls/issues) to see if +2. Check [GitHub](https://github.com/Mbed-TLS/mbedtls/issues) to see if your issue has already been reported. If not, … 3. If the issue is a security risk (for example: buffer overflow, data leak), please report it confidentially as described in [`SECURITY.md`](SECURITY.md). If not, … -4. Please [create an issue on on GitHub](https://github.com/ARMmbed/mbedtls/issues). +4. Please [create an issue on on GitHub](https://github.com/Mbed-TLS/mbedtls/issues). Please do not use GitHub for support questions. If you want to know how to do something with Mbed TLS, please see [`SUPPORT.md`](SUPPORT.md) for available documentation and support channels. |