https://github.com/NagyDonat created 
https://github.com/llvm/llvm-project/pull/90216

It seems that the description of the SEI CERT rules was moved from 
`www.securecoding.cert.org` to `wiki.sei.cmu.edu` and the page IDs were not 
preserved during the transition.

However, the old domain name redirects to the new one and permalinks derived 
from the name of the rule still work, so I kept using the old domain name to be 
consistent with other documentation files using it.

>From e1ff9f4c97e1f4e83c4ab3679982e68f0f470401 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Don=C3=A1t=20Nagy?= <donat.n...@ericsson.com>
Date: Fri, 26 Apr 2024 15:56:46 +0200
Subject: [PATCH] [clang-tidy][NFC] Fix broken link in documentation of
 cert-env33-c

It seems that the description of the SEI CERT rules was moved from
`www.securecoding.cert.org` to `wiki.sei.cmu.edu` and the page IDs were
not preserved during the transition.

However, the old domain name redirects to the new one and permalinks
derived from the name of the rule still work, so I kept using the old
domain name to be consistent with other documentation files using it.
---
 clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst 
b/clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst
index c5321b07f7f84d..9271c9ecccc00c 100644
--- a/clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst
+++ b/clang-tools-extra/docs/clang-tidy/checks/cert/env33-c.rst
@@ -10,4 +10,4 @@ but does not actually attempt to execute a command.
 
 This check corresponds to the CERT C Coding Standard rule
 `ENV33-C. Do not call system()
-<https://www.securecoding.cert.org/confluence/pages/viewpage.action?pageId=2130132>`_.
+<https://www.securecoding.cert.org/confluence/display/c/ENV33-C.+Do+not+call+system()>`_.

_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to