[Lldb-commits] [PATCH] D116351: Update Bug report URL to Github Issues

[Chuanqi Xu via Phabricator via lldb-commits]

ChuanqiXu marked 14 inline comments as done.
ChuanqiXu added inline comments.


================
Comment at: clang/www/c_status.html:75-76
 
-<p>The <a href="https://bugs.llvm.org/">LLVM bug tracker</a> contains a
-Clang C component that tracks known bugs with Clang's language
+<p>The <a href="https://github.com/llvm/llvm-project/issues/">LLVM Issues</a> contains
+issuses labeled with c/c11/c18/c2x that tracks known bugs with Clang's language
 conformance.</p>
----------------
Quuxplusone wrote:
> 
I use the lower-case 'c' to keep consistent with GitHub labels.


================
Comment at: clang/www/cxx_status.html:79-81
+<p>The <a href="https://github.com/llvm/llvm-project/issues/">LLVM Issues</a> contains
+issues labelled with c++/c++11/c++14/c++17/c++20 that track known bugs with Clang's
+language conformance labelled in each language mode.</p>
----------------
Quuxplusone wrote:
> (I think `, "C++17", "C++20", "C++23"` would just be redundant/noise here, and would imply a thankless task for someone to go update this list every 3 years. Better to just cap it at one or two labels. The reader can be trusted to figure out that C++20 issues should be labeled with `C++20`.)
I use the lower-case 'c' to keep consistent with GitHub labels.


================
Comment at: lld/docs/_templates/indexsidebar.html:3-4
 
 <p>lld bugs should be reported at the
-  LLVM <a href="https://bugs.llvm.org/">Bugzilla</a>.</p>
+  LLVM <a href="https://github.com/llvm/llvm-project/issues/">Issues</a>.</p>
----------------
MaskRay wrote:
> Quuxplusone wrote:
> > 
> While here, mention the labels: lld:COFF lld:ELF lld:MachO lld:wasm.
I found label lld would cover the sub-labels.


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

https://reviews.llvm.org/D116351