[PATCH] D155081: Specify the developer policy around links to external resources

tonic added a comment. @lattner Please review. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D155081/new/ https://reviews.llvm.org/D155081 ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/

[Lldb-commits] [PATCH] D156949: [lldb] Update LLDB Code Ownership

tonic added a comment. Comment at: lldb/CodeOwners.rst:7-8 +particular part of LLDB are reviewed, either by themself or by someone else. +They are also the gatekeepers for their part of LLDB, with the final word on +what goes in or not. + JDevlieghere wrote: >

[Lldb-commits] [PATCH] D156949: [lldb] Update LLDB Code Ownership

tonic added a comment. Since you are going to the effort of changing the CodeOwners file format from what is in LLVM, can you go ahead and add Discourse and Discord handles? It is often very helpful to tag someone on Discourse/Discord. I'll be proposing this change for LLVM soon. CHANGES SIN

[PATCH] D155081: Specify the developer policy around links to external resources

tonic added a comment. As I mentioned on the Discourse thread, but if this policy change is made, there should be some discussion about if this applies retroactively. Making a note here, because it probably should be included in the changes to Developer Policy if the radar links are not removed

[PATCH] D132550: Changes to code ownership in clang and clang-tidy

tonic added a comment. Moving to GitHub PRs is the path forward. Let's save ourselves some work and add them now. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D132550/new/ https://reviews.llvm.org/D132550 _

[PATCH] D128766: Update references to Discourse instead of the mailing lists.

This revision was landed with ongoing or failed builds. This revision was automatically updated to reflect the committed changes. Closed by commit rGeb1ffd817c3c: Update references to Discourse instead of the mailing lists. (authored by tonic). Changed prior to commit: https://reviews.llvm.org/

[PATCH] D128766: Update references to Discourse instead of the mailing lists.

tonic updated this revision to Diff 441800. tonic added a comment. Fix typos. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D128766/new/ https://reviews.llvm.org/D128766 Files: clang/docs/ExternalClangExamples.rst clang/www/get_involved.html

[PATCH] D128766: Update references to Discourse instead of the mailing lists.

tonic created this revision. Herald added a project: All. tonic requested review of this revision. Herald added a reviewer: jdoerfert. Herald added subscribers: cfe-commits, sstefan1. Herald added a project: clang. Update the references to the old Mailman mailing lists to point to Discourse forum

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

tonic added a comment. In D121078#3402469 , @aaron.ballman wrote: > In D121078#3400810 , @SimplyDanny > wrote: > >> @tonic, can you please have another look? > > If @tonic has any additional feedback, we can han

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

tonic added a comment. In D121078#3402469 , @aaron.ballman wrote: > In D121078#3400810 , @SimplyDanny > wrote: > >> @tonic, can you please have another look? > > If @tonic has any additional feedback, we can han

[PATCH] D115907: [misexpect] Re-implement MisExpect Diagnostics

tonic added a comment. This is breaking the docs build with the following warning: "MisExpect.rst:document isn't included in any toctree." By default, docs warnings are treated as errors. Can you fix this? Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.

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

tonic added a comment. In D121078#3367950 , @aaron.ballman wrote: > In D121078#3367289 , @tonic wrote: > >> In D121078#3366825 , >> @aaron.ballman wrote: >> >>> In D1210

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

tonic added a comment. In D121078#3367950 , @aaron.ballman wrote: > In D121078#3367289 , @tonic wrote: > >> In D121078#3366825 , >> @aaron.ballman wrote: >> >>> In D1210

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

tonic added a comment. In D121078#3366825 , @aaron.ballman wrote: > In D121078#3366025 , @tonic wrote: > >> In D121078#3365542 , @SimplyDanny >> wrote: >> >>> In D121078

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

tonic added a comment. In D121078#3365542 , @SimplyDanny wrote: > In D121078#3363856 , @aaron.ballman > wrote: > >> I think we need to retain *some* references to the existing mailing list >> archives. The migr

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

tonic added a comment. In D121078#3366825 , @aaron.ballman wrote: > In D121078#3366025 , @tonic wrote: > >> In D121078#3365542 , @SimplyDanny >> wrote: >> >>> In D121078

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

tonic added a comment. In D121078#3365542 , @SimplyDanny wrote: > In D121078#3363856 , @aaron.ballman > wrote: > >> I think we need to retain *some* references to the existing mailing list >> archives. The migr

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

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

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

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

[PATCH] D112730: [clang-tidy] Add AUTOSAR module

tonic added a comment. Unfortunately our legal counsel has advised that this patch should not be included into LLVM because the exact patent burden is not disclosed. Therefore, we can not accept this patch into LLVM. I am very sorry to have to report this disappointing news. CHANGES SINCE LAS

Re: [lldb-dev] Mailman->Discourse Migration on February 1, 10am PST

As a reminder, this will be happening this morning. Thanks, Tanya > On Jan 29, 2022, at 8:29 AM, Tanya Lattner wrote: > > LLVM Community, > > As referenced in this blog post > <https://blog.llvm.org/posts/2022-01-07-moving-to-discourse/>, we are getting >

Re: [cfe-users] Mailman->Discourse Migration on February 1, 10am PST

As a reminder, this will be happening this morning. Thanks, Tanya > On Jan 29, 2022, at 8:21 AM, Tanya Lattner wrote: > > LLVM Community, > > As referenced in this blog post > <https://blog.llvm.org/posts/2022-01-07-moving-to-discourse/>, we are getting >

Re: [lldb-dev] Mailman->Discourse Migration on February 1, 10am PST

Thank you Paul for pointing this out. I will get this information updated tonight. -Tanya > On Jan 29, 2022, at 9:58 AM, Paul Smith wrote: > > On Sat, 2022-01-29 at 08:29 -0800, Tanya Lattner via lldb-dev wrote: >> We will use the Discourse Migration website to communicate whe

[llvm-announce] Mailman->Discourse Migration on February 1, 10am PST

LLVM Community, As referenced in this blog post , we are getting close to the deadline for migration for some Mailman lists to Discourse. If you are receiving this email from a LLVM Mailman list, then this list will be migrating to D

[lldb-dev] Mailman->Discourse Migration on February 1, 10am PST

LLVM Community, As referenced in this blog post , we are getting close to the deadline for migration for some Mailman lists to Discourse. If you are receiving this email from a LLVM Mailman list, then this list will be migrating to D

[cfe-users] Mailman->Discourse Migration on February 1, 10am PST

LLVM Community, As referenced in this blog post , we are getting close to the deadline for migration for some Mailman lists to Discourse. If you are receiving this email from a LLVM Mailman list, then this list will be migrating to D

[lldb-dev] lldb-dev mailing list moving to LLVM Discourse

The lldb-dev mailing list will be moved to LLVM Discourse under the “LLDB” category (under Subprojects). All archives will be migrated. This list will be no longer be in use starting February 1, 2022. Please see this blog post for all details: https://blog.llvm.org/posts/2022-01-07-moving-to-dis

Re: [cfe-users] cfe-users list moving to LLVM Discourse

> On Jan 12, 2022, at 11:02 AM, Jeffrey Walton wrote: > > > > On Wed, Jan 12, 2022 at 1:00 PM Tanya Lattner via cfe-users > mailto:cfe-users@lists.llvm.org>> wrote: > The cfe-users mailing list will be moved to LLVM Discourse under the “Using > Clang” catego

[llvm-announce] LLVM announce mailing list moving to LLVM Discourse

The llvm-announce mailing list will be moved to LLVM Discourse under the “Announcements” category. All archives will be migrated. This list will be no longer be in use starting February 1, 2022. Please see this blog post for all details: https://blog.llvm.org/posts/2022-01-07-moving-to-discourse

[cfe-users] cfe-users list moving to LLVM Discourse

The cfe-users mailing list will be moved to LLVM Discourse under the “Using Clang” category (under Clang Frontend). All archives will be migrated. This list will be no longer be in use starting February 1, 2022. Please see this blog post for all details: https://blog.llvm.org/posts/2022-01-07-m

Re: [lldb-dev] [llvm-dev] RFC: Code Review Process

Hello! The purpose of this email is to start a discussion about our code review tools. No decisions have been made about changing tools. The idea behind a timeline is so that information could be gathered in a timely manner. The Infrastructure Working Group was formed to bring together community

[llvm-announce] LLVM Bay Area Meetup - Oct 20 (in person), tickets on sale Oct 1

It has been almost 2 years since the last in person LLVM Developers' Meeting. In person discussions and networking are very important to maintaining the health of our community and it is the best way to exchange ideas and build connections. However, due to the current pandemic, having large indo

[lldb-dev] 2021 LLVM Developers' Meeting - Call for Talk Proposals DEADLINE TODAY (5pm PDT)

This is just a friendly reminder that the deadline is today at 5pm PDT. Thanks, Tanya > On Sep 17, 2021, at 2:21 PM, Tanya Lattner wrote: > > Hello! This is an update to let you know that the deadline has been extended > to September 27th at 5pm PDT. > > A couple o

Re: [lldb-dev] 2021 LLVM Developers' Meeting - Call for Talk Proposals DEADLINE EXTENDED to Sept 27

couple weeks on how this will work. Thanks, Tanya > On Sep 7, 2021, at 10:13 PM, Tanya Lattner wrote: > > All developers and users of LLVM and related sub-projects are invited to > present at the 2021 LLVM Developers’ Meeting > <https://llvm.org/devmtg/2021-11/>! The co

[lldb-dev] 2021 LLVM Developers' Meeting - Call for Talk Proposals (Deadline Sept 20)

ort abstract for the website Extended PDF abstract (optional) We highly recommend you consult and follow the guide below when submitting your proposal. Additional details regarding notification and recording timeline will be communicated soon. If you have questions, please contact Tanya Lattner thr

IMPORTANT NOTICE - Subscription to Mailman lists disabled immediately

, Tanya Lattner LLVM Foundation ___ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[cfe-users] IMPORTANT NOTICE - Subscription to Mailman lists disabled immediately

, Tanya Lattner LLVM Foundation___ cfe-users mailing list cfe-users@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-users

[Lldb-commits] IMPORTANT NOTICE - Subscription to Mailman lists disabled immediately

, Tanya Lattner LLVM Foundation ___ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

[lldb-dev] IMPORTANT NOTICE - Subscription to Mailman lists disabled immediately

, Tanya Lattner LLVM Foundation ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[llvm-branch-commits] IMPORTANT NOTICE - Subscription to Mailman lists disabled immediately

, Tanya Lattner LLVM Foundation___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

[llvm-bugs] IMPORTANT NOTICE - Subscription to Mailman lists disabled immediately

, Tanya Lattner LLVM Foundation___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

[PATCH] D36836: [clang-tidy] Implement sonarsource-function-cognitive-complexity check

tonic added a comment. Licensing questions are best sent to the bo...@llvm.org mailing address. Can you reach out there? Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D36836/new/ https://reviews.llvm.org/D36836

Re: [lldb-dev] 2020 Virtual LLVM Developers' Meeting - Call for presentations! (Deadline SOON)

A little more than 24 hours left for proposals! Submit your proposal here: LLVM2020 Submissions <https://hotcrp.llvm.org/usllvm2020/> Thank you for your support of our first virtual LLVM Developers’ Meeting! -Tanya > On Jul 12, 2020, at 9:51 AM, Tanya Lattner wrote: > > T

Re: [lldb-dev] 2020 Virtual LLVM Developers' Meeting - Call for presentations! (Deadline EXTENDED)

The deadline has been extended until July 20 11:59PM PDT. Thanks, Tanya > On Jun 12, 2020, at 5:07 PM, Tanya Lattner wrote: > > All developers and users of LLVM and related sub-projects are invited to > present at the first virtual 2020 LLVM Developers’ Meeting > <http://ll

[lldb-dev] 2020 Virtual LLVM Developers' Meeting - Call for presentations!

All developers and users of LLVM and related sub-projects are invited to present at the first virtual 2020 LLVM Developers’ Meeting ! We are looking for the following proposals: Technical Talks (25-30 minutes including Q&A): Talks on: LLVM Infrastructure,Clang an

[lldb-dev] New Dates for 2020 Virtual LLVM Dev Mtg

. Thanks, Tanya Lattner LLVM Dev Mtg Organizer President - LLVM Foundation___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] 2020 US LLVM Developers' Meeting - Announcement & Feedback Needed

, and advice. If you have any questions, please feel free to reach out to me personally or on the mailing lists. Thank you, Tanya Lattner President LLVM Foundation___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] 2020 US LLVM Developers' Meeting - September 28-29

The LLVM Foundation is pleased to announce the 14th annual LLVM Developers’ Meeting in the Bay Area on September 28-29 in San Jose, CA. We will have additional events on September 27th in the afternoon/evening which be announced when available. The LLVM Develo

[lldb-dev] Code of Conduct Next Steps - Community feedback needed

LLVM Community, The LLVM Code of Conduct has been in draft mode for several years now. In order to finalize the Code of Conduct, there are 3 steps left to complete: Draft an Incident Response Guide. This guide is intended for someone who is considering reporting a potential code of conduct vio

Re: [lldb-dev] [llvm-dev] [cfe-dev] December LLVM bay-area social is this Thursday!

In case Steins doesn't work out.. BJs in Cupertino has a large space for groups but that would mean closer to Cupertino area. -Tanya > On Dec 28, 2019, at 8:50 PM, Eric Christopher via llvm-dev > wrote: > > Still a bit of a Twitter thread too. A few more options maybe if we want to > move t

Re: [lldb-dev] LLDB Website is not being updated

I’ll have to check the status of moving the scripts over and what is going on. But yes, this is all related to moving to GitHub and modifying scripts that used to be either on a post-commit hook or nightly cron. -Tanya > On Nov 21, 2019, at 3:04 PM, Jonas Devlieghere wrote: > > I see a bunch

[lldb-dev] (Deadline Monday!) Re: 2019 LLVM Dev Mtg (Bay Area) - Call for presentations

This is just a friendly reminder that the deadline is on Monday, August 12th. Thanks, Tanya > On Jul 2, 2019, at 8:54 AM, Tanya Lattner wrote: > > All developers and users of LLVM and related sub-projects are invited to > present at the 2019 LLVM Developers’ Meeting - Bay A

[lldb-dev] 2019 LLVM Dev Mtg (Bay Area) - Call for presentations

All developers and users of LLVM and related sub-projects are invited to present at the 2019 LLVM Developers’ Meeting - Bay Area . We are looking for the following proposals: Technical Talks (25-30 minutes including Q&A): - On LLVM Infrastructure,Clang and all re

[lldb-dev] 2019 LLVM Developers' Meeting (Bay Area) - Registration open

The LLVM Foundation is pleased to announce the 13th annual LLVM Developers’ Meeting in the Bay Area on October 22-23, 2019 in San Jose, CA. Registration is now open! https://www.eventbrite.com/e/2019-llvm-developers-meeting-bay-area-tickets-63481303287

Re: [lldb-dev] LLDB Website

ed it back. -Tanya > > Thank, > Jonas > > On Tue, May 7, 2019 at 4:08 PM Tanya Lattner <mailto:tanyalatt...@llvm.org>> wrote: > Ok, I believe everything should be working. So the cpp ref and python ref are > generated nightly. Sphinx/web is done post-commit. I just

Re: [lldb-dev] LLDB Website

t. I > checked the www-scripts mailing list but I don't see any failures for LLDB. > Do you know what's up here? > > Thanks, > Jonas > > On Tue, May 7, 2019 at 12:19 AM Tanya Lattner <mailto:tanyalatt...@llvm.org>> wrote: > Ignore this. svn wasn’t actual

Re: [lldb-dev] LLDB Website

Ignore this. svn wasn’t actually updating the src tree. It works! I just need doxygen script to finish and it will be confirmed tonight. -Tanya > On May 6, 2019, at 11:55 PM, Tanya Lattner wrote: > > I’m not sure it is working. To clarify, nothing in LLVM should be compiled to &g

Re: [lldb-dev] LLDB Website

let me know if there's anything I can do to help. > > Thanks, > Jonas > > On Wed, May 1, 2019 at 10:40 PM Tanya Lattner <mailto:tanyalatt...@llvm.org>> wrote: > I will give this a shot. I did remove the changes before to prevent any issue. > > -Tanya >

Re: [lldb-dev] LLDB Website

/lib${LLVM_LIBDIR_SUFFIX}/python2.7/site-packages > COMMENT "Generating LLDB Python API reference with epydoc" VERBATIM > ) > endif(EPYDOC_EXECUTABLE) > > > > -Original Message- > > From: lldb-dev > <mailto:lldb-dev-boun...@lists.llvm.or

Re: [lldb-dev] LLDB Website

> On Apr 23, 2019, at 5:06 PM, Jonas Devlieghere wrote: > > > > On Tue, Apr 23, 2019 at 5:00 PM Tanya Lattner <mailto:tanyalatt...@llvm.org>> wrote: > > >> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere > <mailto:jo...@devlieghere.com>>

Re: [lldb-dev] LLDB Website

> On Apr 23, 2019, at 11:54 AM, Jonas Devlieghere wrote: > > Hey Tanya, > > On Tue, Apr 23, 2019 at 11:51 Tanya Lattner <mailto:tanyalatt...@llvm.org>> wrote: > Jonas, > > Ignore what I said before as these do need to be separate targets. It appears >

Re: [lldb-dev] LLDB Website

23, 2019, at 11:45 AM, Tanya Lattner wrote: > > Anytime new targets are added, the script has to be modified. Is there a way > you can put them all under a top level html target? Or is there a reason not > to? > > -Tanya > >> On Apr 19, 2019, at 12:17 PM,

Re: [lldb-dev] LLDB Website

Anytime new targets are added, the script has to be modified. Is there a way you can put them all under a top level html target? Or is there a reason not to? -Tanya > On Apr 19, 2019, at 12:17 PM, Jonas Devlieghere wrote: > > Hey Tanya, > > Thanks again for migrating the LLDB website so it is

[lldb-dev] Mentors and projects needed for Season of Docs

LLVM Developers, Google has a new program called Season of Docs . To summarize, this program brings together open source communities and technical writers to the benefit of both. Open source communities are paired with technical writers on technica

[lldb-dev] Moderator needed for lldb-commits

LLDB Developers, Moderators are needed for the lldb-commits mailing list. Is anyone interested in helping out? Thanks, Tanya ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] 2018 LLVM Developers' Meeting - Bay Area, October 17-18

The LLVM Foundation is pleased to announce the 12th annual LLVM Developers’ Meeting in the Bay Area on October 17-18, 2018 in San Jose, CA. Registration will be opening F

[lldb-dev] Need one more moderator volunteer!

Can anyone help with this session? Session 10 (2:10-3:40PM, General Session) Adding Index‐While‐Building and Refactoring to Clang Advancing Clangd: Bringing persisted indexing to Clang tooling Thanks, Tanya > On Oct 10, 2017, at 5:27 PM, Tanya Lattner wrote: > > Just 2 more slot

Re: [lldb-dev] Moderators for the 2017 LLVM Developers' Mtg Needed! (2 slots left!)

PM, Tanya Lattner wrote: > > Thank you for those who have volunteered. I am still in need of people for > the following sessions: > > Session 7 (10:00-10:45AM, Technical Track) > eval() in C++ > > Session 8 (11:10AM-12:40PM, General Session) > Implementing Swift Gene

Re: [lldb-dev] Moderators for the 2017 LLVM Developers' Mtg Needed!

Obfuscator -Tanya > On Sep 26, 2017, at 1:49 AM, Tanya Lattner wrote: > > The 2017 LLVM Developers’ Meeting relies on volunteers to keep things running > smoothly. Moderators are critical to this as they keep speakers on track and > facilitate Q&A after the talk. I’m lo

[lldb-dev] Moderators for the 2017 LLVM Developers' Mtg Needed!

The 2017 LLVM Developers’ Meeting relies on volunteers to keep things running smoothly. Moderators are critical to this as they keep speakers on track and facilitate Q&A after the talk. I’m looking for community members who would be attending specific talks anyway, to volunteer to moderate the s

[lldb-dev] 2017 LLVM Dev Meeting - Schedule Online, Registration Closing & Room Block Expiring

All, The 2017 LLVM Developers’ Meeting registration will be closing soon! Please make sure you are registered and tell your friends that they don’t want to miss the opportunity to attend the largest gathering of LLVM Developers. https://llvm.org/devmtg/2017-10/ https://www.eventbrite.com/e/2017

[lldb-dev] Session Volunteers for Hackers Lab Needed!

All, We need volunteers for the Hacker’s Lab at the upcoming 2017 LLVM Developers’ Meeting! The Hacker’s Lab is for small groups to form to discuss topics or work on problems. Please let me know ASAP if you will able to volunteer so I can add your topic to the online listing and make appropriat

[lldb-dev] IMPORTANT: *.llvm.org certificates being renewed (impacts SVN) FRIDAY Sept 22

All, The following llvm.org certificates will be renewed tomorrow, Friday Sept 22nd at ~7:30AM PDT. bugs.llvm.org clang-analyzer.llvm.org clang.llvm.org compiler-rt.llvm.org

Re: r308044 - Add documentation for @available

> On Jul 18, 2017, at 8:07 AM, Nico Weber wrote: > > On Mon, Jul 17, 2017 at 8:39 AM, Aaron Ballman > wrote: > On Sun, Jul 16, 2017 at 7:49 PM, Nico Weber > wrote: > > Aaron, https://clang.llvm.org/docs/AttributeReference.html#availabi

Re: [cfe-users] [llvm-dev] LLVM docs links broken

Added redirect and also removed doxygen from robots.txt -Tanya > On Jun 30, 2017, at 10:20 PM, Tim Northover wrote: > > Hi, > > I think we need a fix to this as soon as possible. I know people say > that out of date documentation is worse than none, but I think that's > horribly false in this

[lldb-dev] IMPORTANT: LLVM.org server move complete (SVN impact please read)

LLVMers, We have completed the move to the new server for LLVM.org. One casualty of this move was that svn.llvm.org was NOT enabled at this time. There is a new certificate for LLVM.org and HTTPS is enabled for the website. We know of a few issues with some of the webpages but will be working

[lldb-dev] IMPORTANT: LLVM.org server move on June 24th! (SVN impact)

LLVMers, The LLVM.org server which hosts SVN, GIT mirror, documentation, and the main LLVM.org website is moving to a new server on June 24th. As a result of the move commit access will be locked out beginning 09:00PDT on the 24th. We hope to have the mo

[lldb-dev] LLVM.org (SVN, web) DOWNTIME May 20th (7AM CDT -> 1PM CDT)

FYI, The llvm.org server will be down May 20th from 7AM CDT to 1PM CDT. SVN and llvm.org webpages will be unavailable. Please note that some websites and services (Mailing lists, Clang and other sub-projects, APT, releases, Bugzilla) are hosted by other servers and are not impacted. I apologiz

[lldb-dev] LLVM Bugzilla MOVED to bugs.llvm.org

All, http://llvm.org/bugs has moved to bugs.llvm.org . You will be redirected if you attempted to access via the old URL, but please update your bookmarks as well. HTTPS access to bugzilla is now updated to a new SSL certificate. If you experience

[lldb-dev] [SERVER UPDATE] Moving openmp, clang, clang-analyzer, libcxxabi, libcxx ... websites to new server

All, The following websites will be moving to a new web server in the next few days: clang.llvm.org clang-analyzer.llvm.org compiler-rt.llvm.org dragonegg.llvm.org klee.llvm.org <

[lldb-dev] New Hackers Lab - Volunteers and Code Owners Needed

All, We are trying something different at the Hackers Lab at the upcoming LLVM Developers’ Meeting and need volunteers to help make this a success! The reason behind the change is that we want to make the Hackers Lab more inviting to new developers, make it easier to find the developers you are

[lldb-dev] [IMPORTANT] llvm.org downtime

All, llvm.org <http://llvm.org/> will be unreachable on Sunday, October 2 from 3:00AM CDT to 7:00AM CDT in order to perform network upgrades. Thanks, Tanya Lattner ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/c

[llvm-announce] Announcing the next LLVM Foundation Board of Directors

The LLVM Foundation is pleased to announce its new Board of Directors: Chandler Carruth Hal Finkel Arnaud de Grandmaison David Kipping Anton Korobeynikov Tanya Lattner Chris Lattner John Regehr Three new members and five continuing members were elected to the eight person board. The new board

Re: [lldb-dev] [IMPORTANT] bugzilla email notification enabled

FYI, email notification is re-enabled for bugzilla. Please note that user self-registration is still disabled for now and you should email llvm-ad...@lists.llvm.org <mailto:llvm-ad...@lists.llvm.org> for account creation. Thanks, Tanya > On Aug 29, 2016, at 11:59 AM, Tanya Lattn

[lldb-dev] [IMPORTANT] Disabling bugzilla email notification temporarily

Bugzilla email notification will be turned off until spam cleanup can be handled. Thanks, Tanya ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] Closing spam bugs has a consequence, be aware

Paul, Please don’t mass close the bugs. I’m going to turn off bugzilla mail and then do the cleanup. -Tanya > On Aug 29, 2016, at 11:53 AM, Robinson, Paul via llvm-dev > wrote: > > I just went in and bulk-closed a dozen or so of today's spam bugs. > This made me realize that doing so sends a

[llvm-announce] Interested in being on the LLVM Foundation Board of Directors?

info/llvm-foundation>). This announcement was posted here to ensure we reach as many LLVM community members as possible. Thanks, Tanya Lattner President, LLVM Foundation___ llvm-announce mailing list llvm-announce@lists.llvm.org http://lists.llvm

Re: [lldb-dev] [llvm-dev] GitHub anyone?

> On Jun 2, 2016, at 12:18 PM, Mehdi Amini wrote: > > >> On Jun 2, 2016, at 9:21 AM, Tanya Lattner via llvm-dev >> wrote: >> >> I personally find this email thread very hard to follow and read (this isn’t >> anyones fault.. its just a lot of r

Re: [lldb-dev] [cfe-dev] [llvm-dev] GitHub anyone?

> On Jun 2, 2016, at 3:59 PM, Brian Cain wrote: > >> On Thu, Jun 2, 2016 at 11:21 AM, Tanya Lattner via cfe-dev >> wrote: >> I personally find this email thread very hard to follow and read (this isn’t >> anyones fault.. its just a lot of replies). I am sure

Re: [lldb-dev] [llvm-dev] GitHub anyone?

I personally find this email thread very hard to follow and read (this isn’t anyones fault.. its just a lot of replies). I am sure others do as well. I think it would be good to have a form/survey of some sort that can get feedback from users such as: who they are, how they use LLVM/contribution

Re: [lldb-dev] lists.llvm.org server maintenance, Friday Dec 18 @10:30 PST

The server maintenance is complete and lists should be operational. Thanks, Tanya > On Dec 17, 2015, at 12:06 PM, Tanya Lattner wrote: > > All, > > The server that runs the mailing lists will be down for maintenance starting > Friday Dec 18th at 10:30PM PST. I do not expe

Re: [cfe-users] lists.llvm.org server maintenance, Friday Dec 18 @10:30 PST

The server maintenance is complete and lists should be operational. Thanks, Tanya > On Dec 17, 2015, at 12:06 PM, Tanya Lattner wrote: > > All, > > The server that runs the mailing lists will be down for maintenance starting > Friday Dec 18th at 10:30PM PST. I do not expe

[lldb-dev] lists.llvm.org server maintenance, Friday Dec 18 @10:30 PST

All, The server that runs the mailing lists will be down for maintenance starting Friday Dec 18th at 10:30PM PST. I do not expect a long downtime, but please keep this in mind if you see any issues with the lists during this period. I will send an email once I am finished. No other services sh

[cfe-users] lists.llvm.org server maintenance, Friday Dec 18 @10:30 PST

All, The server that runs the mailing lists will be down for maintenance starting Friday Dec 18th at 10:30PM PST. I do not expect a long downtime, but please keep this in mind if you see any issues with the lists during this period. I will send an email once I am finished. No other services sh

Re: [llvm-bugs] [Bug 25616] New: bug

Vedant, From what I understand, bugzilla doesn’t allow me to block users. Deleting seems possible but there are some warnings about corrupting the database (I will investigate more). I have deleted the attachments though. Thanks, Tanya > On Nov 25, 2015, at 8:04 AM, Vedant Kumar wrote: > > H

[llvm-bugs] Change to list permissions/announce only

All, I plan to make the llvm-bugs announce-only (by bugzilla only). This will cut down on the moderation done for a list that is really only used by bugzilla. Does anyone have any objections to this? Thanks, Tanya ___ llvm-bugs mailing list llvm-bug

[libcxx] r246912 - Remove test commit.

Author: tbrethou Date: Sat Sep 5 00:38:50 2015 New Revision: 246912 URL: http://llvm.org/viewvc/llvm-project?rev=246912&view=rev Log: Remove test commit. Modified: libcxx/trunk/docs/README.txt Modified: libcxx/trunk/docs/README.txt URL: http://llvm.org/viewvc/llvm-project/libcxx/trunk/docs

[libcxx] r246911 - Test temporary commit.

Author: tbrethou Date: Sat Sep 5 00:34:27 2015 New Revision: 246911 URL: http://llvm.org/viewvc/llvm-project?rev=246911&view=rev Log: Test temporary commit. Modified: libcxx/trunk/docs/README.txt Modified: libcxx/trunk/docs/README.txt URL: http://llvm.org/viewvc/llvm-project/libcxx/trunk/

[lldb-dev] Moderator needed

Hello! I am looking for 1-2 volunteers to help moderate the lldb-dev and lldb-commits mailing lists. Please let me know if you can help! Thanks, Tanya ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-

[Lldb-commits] Moderator needed

Hello! I am looking for 1-2 volunteers to help moderate the lldb-dev and lldb-commits mailing lists. Please let me know if you can help! Thanks, Tanya ___ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listin

  1   2   3   4   5   6   7   >