<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Dec 11, 2021 at 6:41 AM Shoaib Meenai via flang-dev <<a href="mailto:flang-dev@lists.llvm.org">flang-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Thank you for all the work to make this happen!<br>
<br>
I apologize if I missed this somewhere, but what's the solution for subscribing to issues created with specific tags? I found <a href="https://github.com/marketplace/actions/issue-label-notifier" rel="noreferrer" target="_blank">https://github.com/marketplace/actions/issue-label-notifier</a> through searching, but that seems to be something that needs to be set up for the repo and not something I set up on my own end.<br></blockquote><div><br></div><div>Same question: my mailbox is exploding right now, how do we manage subscription/notifications?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
On 12/11/21, 3:03 PM, "cfe-dev on behalf of Anton Korobeynikov via cfe-dev" <<a href="mailto:cfe-dev-bounces@lists.llvm.org" target="_blank">cfe-dev-bounces@lists.llvm.org</a> on behalf of <a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a>> wrote:<br>
<br>
Dear Fellow LLVM Developers, Users et al<br>
<br>
I'm happy to announce that the main part of the LLVM Bugzilla =><br>
GitHub migration is complete. I appreciate your patience on this<br>
matter as several unexpected issues happened during the final phase of<br>
the migration. I would like to thank everyone who was involved in<br>
different steps of this migration and additionally I would like to<br>
thank all GitHub engineers without whom this will not be possible.<br>
<br>
There are still some rough edges and known issues. However we are<br>
going to address them post-migration. Feel free to submit your issues<br>
to the shiny new LLVM bugtracker at<br>
<a href="https://github.com/llvm/llvm-project/issues" rel="noreferrer" target="_blank">https://github.com/llvm/llvm-project/issues</a><br>
Use <a href="http://llvm.org/PR" rel="noreferrer" target="_blank">llvm.org/PR</a> links to seamlessly connect "old" and "new" issues.<br>
E.g. <a href="https://llvm.org/PR1000" rel="noreferrer" target="_blank">https://llvm.org/PR1000</a> will redirect to the migrated bugzilla id<br>
1000 and <a href="https://llvm.org/PR52603" rel="noreferrer" target="_blank">https://llvm.org/PR52603</a> is a new github-only issue. All<br>
issues that are migrated from bugzilla are tagged with "bugzilla"<br>
label. All issues related to the post-migration tasks are filed under<br>
<a href="https://github.com/llvm/llvm-project/milestone/1" rel="noreferrer" target="_blank">https://github.com/llvm/llvm-project/milestone/1</a> milestone.<br>
<br>
--<br>
On behalf of LLVM Foundation<br>
Anton Korobeynikov,<br>
_______________________________________________<br>
cfe-dev mailing list<br>
<a href="mailto:cfe-dev@lists.llvm.org" target="_blank">cfe-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev</a> <br>
<br>
_______________________________________________<br>
flang-dev mailing list<br>
<a href="mailto:flang-dev@lists.llvm.org" target="_blank">flang-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/flang-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/flang-dev</a><br>
</blockquote></div></div>