[llvm] [docs] Replace mailing list with Discourse (PR #106556)

[Tulio Magno Quites Machado Filho via llvm-commits]

https://github.com/tuliom created https://github.com/llvm/llvm-project/pull/106556

RFCs are now expected to be sent to the LLVM Discourse forums.

>From beb31b72f4befdefb147d695a3d32abcd3c846a4 Mon Sep 17 00:00:00 2001
From: Tulio Magno Quites Machado Filho <tuliom at redhat.com>
Date: Thu, 29 Aug 2024 10:23:28 -0300
Subject: [PATCH] [docs] Replace mailing list with Discourse

RFCs are now expected to be sent to the LLVM Discourse forums.
---
 llvm/docs/CodeReview.rst | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/llvm/docs/CodeReview.rst b/llvm/docs/CodeReview.rst
index 0128e37465de32..4ce9c8eddaa268 100644
--- a/llvm/docs/CodeReview.rst
+++ b/llvm/docs/CodeReview.rst
@@ -89,7 +89,8 @@ When Is an RFC Required?
 Some changes are too significant for just a code review. Changes that should
 change the LLVM Language Reference (e.g., adding new target-independent
 intrinsics), adding language extensions in Clang, and so on, require an RFC
-(Request for Comment) email on the project's ``*-dev`` mailing list first. For
+(Request for Comment) topic on the `LLVM Discourse forums
+<https://discourse.llvm.org>`_ first. For
 changes that promise significant impact on users and/or downstream code bases,
 reviewers can request an RFC achieving consensus before proceeding with code
 review. That having been said, posting initial patches can help with