[Lldb-commits] [PATCH] D121078: Replace links to archived mailing lists by links to Discourse forums

[Tanya Lattner via Phabricator via lldb-commits]

tonic requested changes to this revision.
tonic added a comment.

Thank you so much for doing this! I have added some comments inline that I would like changed.



================
Comment at: clang/README.txt:22
 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/
----------------
Should this be "on" the Clang forum? Versus in. 


================
Comment at: clang/www/analyzer/menu.html.incl:37
   <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>
----------------
We should retain a link to the forums here. I would change the heading to Mailing List & Forums and then add the link here too. 


================
Comment at: clang/www/demo/index.cgi:23
 my $MAILADDR        = 'sabre at 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';
----------------
I would change to "on" the forums.


================
Comment at: flang/docs/GettingInvolved.md:23-24
 
-  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.
 
----------------
This is worded like it is a mailing list. I would reword to something like "Flang forums are for technical discussions, questions about writing code for, or using Flang tools."


================
Comment at: flang/docs/GettingInvolved.md:52
     If you can not access the Google Doc, please send an email to Alexis Perry-Holby at aperry at 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`.
 
----------------
I would say "on" the Flang forum.

As a side note, all the old meeting minutes should be moved to this category. I can add it to my TODO list. 


================
Comment at: llvm/docs/ExtendingLLVM.rst:17-18
 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
----------------
"on" the forums. Sorry, just my preference :)


================
Comment at: llvm/docs/tutorial/MyFirstLanguageFrontend/LangImpl10.rst:90-91
 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
----------------
Discourse uses a little different terminology. I would change this to "please post on the LLVM forums"


================
Comment at: llvm/docs/tutorial/MyFirstLanguageFrontend/LangImpl10.rst:169
 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.
----------------
Ask "on"


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D121078/new/

https://reviews.llvm.org/D121078