SimplyDanny created this revision. SimplyDanny added a reviewer: tonic. Herald added subscribers: libcxx-commits, arphaman. Herald added a reviewer: sscalpone. Herald added projects: libunwind, Flang, All. Herald added a reviewer: libunwind. SimplyDanny requested review of this revision. Herald added subscribers: cfe-commits, llvm-commits, lldb-commits, Sanitizers, jdoerfert. Herald added projects: clang, Sanitizers, LLDB, libc++, LLVM, clang-tools-extra. Herald added a reviewer: libc++.
Repository: rG LLVM Github Monorepo https://reviews.llvm.org/D121078 Files: clang-tools-extra/README.txt clang/README.txt clang/www/analyzer/menu.html.incl clang/www/demo/index.cgi clang/www/menu.html.incl compiler-rt/www/menu.html.incl flang/docs/GettingInvolved.md libcxx/docs/index.rst libunwind/docs/index.rst lldb/docs/index.rst llvm/docs/Contributing.rst llvm/docs/ExtendingLLVM.rst llvm/docs/tutorial/MyFirstLanguageFrontend/LangImpl10.rst
Index: llvm/docs/tutorial/MyFirstLanguageFrontend/LangImpl10.rst =================================================================== --- llvm/docs/tutorial/MyFirstLanguageFrontend/LangImpl10.rst +++ llvm/docs/tutorial/MyFirstLanguageFrontend/LangImpl10.rst @@ -87,8 +87,8 @@ Have fun - try doing something crazy and unusual. Building a language like everyone else always has, is much less fun than trying something a little crazy or off the wall and seeing how it turns out. If you get -stuck or want to talk about it, feel free to email the `llvm-dev mailing -list <http://lists.llvm.org/mailman/listinfo/llvm-dev>`_: it has lots +stuck or want to talk about it, feel free to open a thread in the `LLVM +forum <https://discourse.llvm.org>`_: it has lots of people who are interested in languages and are often willing to help out. @@ -166,9 +166,8 @@ IR does not itself guarantee safety. The LLVM IR allows unsafe pointer casts, use after free bugs, buffer over-runs, and a variety of other problems. Safety needs to be implemented as a layer on top of LLVM and, -conveniently, several groups have investigated this. Ask on the `llvm-dev -mailing list <http://lists.llvm.org/mailman/listinfo/llvm-dev>`_ if -you are interested in more details. +conveniently, several groups have investigated this. Ask in the `LLVM +forum <https://discourse.llvm.org>`_ if you are interested in more details. Language-Specific Optimizations ------------------------------- Index: llvm/docs/ExtendingLLVM.rst =================================================================== --- llvm/docs/ExtendingLLVM.rst +++ llvm/docs/ExtendingLLVM.rst @@ -14,8 +14,8 @@ When you come to this realization, stop and think. Do you really need to extend LLVM? Is it a new fundamental capability that LLVM does not support at its current incarnation or can it be synthesized from already pre-existing LLVM -elements? If you are not sure, ask on the `LLVM-dev -<http://lists.llvm.org/mailman/listinfo/llvm-dev>`_ list. The reason is that +elements? If you are not sure, ask in the `LLVM forum +<https://discourse.llvm.org>`_ list. The reason is that extending LLVM will get involved as you need to update all the different passes that you intend to use with your extension, and there are ``many`` LLVM analyses and transformations, so it may be quite a bit of work. Index: llvm/docs/Contributing.rst =================================================================== --- llvm/docs/Contributing.rst +++ llvm/docs/Contributing.rst @@ -147,7 +147,7 @@ .. __: http://www.aosabook.org/en/llvm.html -.. _Developer's List (llvm-dev): http://lists.llvm.org/mailman/listinfo/llvm-dev +.. _Forum: https://discourse.llvm.org .. _irc.oftc.net: irc://irc.oftc.net/llvm .. _beginner: https://github.com/llvm/llvm-project/issues?q=is%3Aopen+is%3Aissue+label%3Abeginner .. _bug tracker: https://github.com/llvm/llvm-project/issues @@ -155,4 +155,3 @@ .. _git-clang-format: https://reviews.llvm.org/source/llvm-github/browse/main/clang/tools/clang-format/git-clang-format .. _LLVM's Phabricator: https://reviews.llvm.org/ .. _LLVM's Open Projects page: https://llvm.org/OpenProjects.html#what -.. _LLVM Developer's mailing list: http://lists.llvm.org/mailman/listinfo/llvm-dev Index: lldb/docs/index.rst =================================================================== --- lldb/docs/index.rst +++ lldb/docs/index.rst @@ -102,10 +102,10 @@ See the :doc:`LLDB Build Page <resources/build>` for build instructions. -Discussions about LLDB should go to the `lldb-dev -<http://lists.llvm.org/mailman/listinfo/lldb-dev>`__ mailing list. Commit +Discussions about LLDB should go to the `LLDB forum +<https://discourse.llvm.org/c/subprojects/lldb>`__. Commit messages are automatically sent to the `lldb-commits -<http://lists.llvm.org/mailman/listinfo/lldb-commits>`__ mailing list , and +<http://lists.llvm.org/mailman/listinfo/lldb-commits>`__ mailing list, and this is also the preferred mailing list for patch submissions. See the :doc:`Projects page <status/projects>` if you are looking for some Index: libunwind/docs/index.rst =================================================================== --- libunwind/docs/index.rst +++ libunwind/docs/index.rst @@ -86,13 +86,13 @@ If you want to contribute a patch to libunwind, the best place for that is `Phabricator <https://llvm.org/docs/Phabricator.html>`_. Please include [libunwind] in the subject and add `cfe-commits` as a subscriber. Also make sure you are subscribed to the -`cfe-commits mailing list <http://lists.llvm.org/mailman/listinfo/cfe-commits>`_. +`Runtimes category <https://discourse.llvm.org/tags/c/runtimes>`_ and look for the tag "libunwind". **Discussion and Questions** Send discussions and questions to the -`cfe-dev mailing list <http://lists.llvm.org/mailman/listinfo/cfe-dev>`_. -Please include [libunwind] in the subject. +`Runtimes forum <https://discourse.llvm.org/tags/c/runtimes>`_. +Please add the tag "libunwind" to your post. Quick Links Index: libcxx/docs/index.rst =================================================================== --- libcxx/docs/index.rst +++ libcxx/docs/index.rst @@ -206,12 +206,11 @@ If you want to contribute a patch to libc++, the best place for that is `Phabricator <https://llvm.org/docs/Phabricator.html>`_. Please add `libcxx-commits` as a subscriber. -Also make sure you are subscribed to the `libcxx-commits mailing list <http://lists.llvm.org/mailman/listinfo/libcxx-commits>`_. +Also make sure you are subscribed to the `libcxx forum <https://discourse.llvm.org/c/runtimes/libcxx>`_. **Discussion and Questions** -Send discussions and questions to the -`libcxx-dev mailing list <http://lists.llvm.org/mailman/listinfo/libcxx-dev>`_. +Send discussions and questions to the `libcxx forum <https://discourse.llvm.org/c/runtimes/libcxx>`_. Quick Links Index: flang/docs/GettingInvolved.md =================================================================== --- flang/docs/GettingInvolved.md +++ flang/docs/GettingInvolved.md @@ -16,11 +16,11 @@ Please feel free to join the mailing list or the slack channel for discussions related to development of Flang. To understand the status of various developments in Flang please join the respective call. -## Mailing Lists +## Forum and Mailing Lists -[Developer's List (flang-dev)](http://lists.llvm.org/mailman/listinfo/flang-dev) +[Forum](https://discourse.llvm.org/c/subprojects/flang) - This list is for people who want to be included in technical discussions related to Flang. People post to this list when they have questions about writing code + This forum is for people who want to be included in technical discussions related to Flang. People post in this forum when they have questions about writing code for or using the Flang tools. It is relatively low volume. @@ -49,7 +49,7 @@ - Time: On Wednesdays 8:30 Pacific Time, on the weeks alternating with regular Flang Community Technical Biweekly Call. - Meeting minutes are available in this [Google Doc](https://docs.google.com/document/d/10T-S2J3GrahpG4Ooif93NSTz2zBW0MQc_RlwHi0-afY/edit?usp=sharing). If you can not access the Google Doc, please send an email to Alexis Perry-Holby at ape...@lanl.gov requesting to be added to the access list. -- Minutes from older meetings were sent to [flang-dev](http://lists.llvm.org/mailman/listinfo/flang-dev). Search for `Flang Biweekly Sync - Notes`. +- Minutes from older meetings were posted in the [Flang forum](https://discourse.llvm.org/c/subprojects/flang). Search for `Flang Biweekly Sync - Notes`. ### Flang Community Technical Biweekly Call Index: compiler-rt/www/menu.html.incl =================================================================== --- compiler-rt/www/menu.html.incl +++ compiler-rt/www/menu.html.incl @@ -10,7 +10,7 @@ <div class="submenu"> <label>Quick Links</label> - <a href="http://lists.llvm.org/mailman/listinfo/llvm-dev";>llvm-dev</a> + <a href="https://discourse.llvm.org";>LLVM Forum</a> <a href="http://lists.llvm.org/mailman/listinfo/llvm-commits";>llvm-commits</a> <a href="http://llvm.org/bugs/";>Bug Reports</a> <a href="https://github.com/llvm/llvm-project/tree/main/compiler-rt/";>Browse Sources</a> Index: clang/www/menu.html.incl =================================================================== --- clang/www/menu.html.incl +++ clang/www/menu.html.incl @@ -33,8 +33,7 @@ <div class="submenu"> <label>Communication</label> - <a href="http://lists.llvm.org/mailman/listinfo/cfe-users";>cfe-users List</a> - <a href="http://lists.llvm.org/mailman/listinfo/cfe-dev";>cfe-dev List</a> + <a href="https://discourse.llvm.org/c/clang";>Clang Forum</a> <a href="http://lists.llvm.org/mailman/listinfo/cfe-commits";>cfe-commits List</a> <a href="https://github.com/llvm/llvm-project/issues";>Bug Reports</a> <a href="http://planet.clang.org/";>Planet Clang</a> Index: clang/www/demo/index.cgi =================================================================== --- clang/www/demo/index.cgi +++ clang/www/demo/index.cgi @@ -20,7 +20,7 @@ my $LOGFILE = "$ROOT/log.txt"; my $FORM_URL = 'index.cgi'; my $MAILADDR = 'sa...@nondot.org'; -my $CONTACT_ADDRESS = 'Questions or comments? Email the <a href="http://lists.llvm.org/mailman/listinfo/llvm-dev";>LLVM-dev mailing list</a>.'; +my $CONTACT_ADDRESS = 'Questions or comments? Discuss in the <a href="https://discourse.llvm.org";>LLVM forum</a>.'; my $LOGO_IMAGE_URL = 'cathead.png'; my $TIMEOUTAMOUNT = 20; $ENV{'LD_LIBRARY_PATH'} = '/home/vadve/shared/localtools/fc1/lib/'; Index: clang/www/analyzer/menu.html.incl =================================================================== --- clang/www/analyzer/menu.html.incl +++ clang/www/analyzer/menu.html.incl @@ -34,7 +34,6 @@ <li> Mailing Lists <ul> - <li><a href="http://lists.llvm.org/mailman/listinfo/cfe-dev";>cfe-dev</a></li> <li><a href="http://lists.llvm.org/mailman/listinfo/cfe-commits";>cfe-commits</a></li> </ul> </li> Index: clang/README.txt =================================================================== --- clang/README.txt +++ clang/README.txt @@ -19,8 +19,8 @@ Information on the LLVM project: http://llvm.org/ If you have questions or comments about Clang, a great place to discuss them is -on the Clang development mailing list: - http://lists.llvm.org/mailman/listinfo/cfe-dev +in the Clang forum: + https://discourse.llvm.org/c/clang/ If you find a bug in Clang, please file it in the LLVM bug tracker: http://llvm.org/bugs/ Index: clang-tools-extra/README.txt =================================================================== --- clang-tools-extra/README.txt +++ clang-tools-extra/README.txt @@ -11,8 +11,8 @@ tree, and in the 'tools/extra' subdirectory of the Clang checkout. All discussion regarding Clang, Clang-based tools, and code in this repository -should be held using the standard Clang mailing lists: - http://lists.llvm.org/mailman/listinfo/cfe-dev +should be held using the standard Clang forum: + https://discourse.llvm.org/c/clang Code review for this tree should take place on the standard Clang patch and commit lists:
_______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
