Chris Johns commented: https://gitlab.rtems.org/rtems/websites/www.rtems.org/-/issues/7#note_119092 A lot of links have moved or changed across a range of sites we control over a lengthy period of time. It is nature of published active data and an evolving project. What makes this link different? The way we operate today is very different to how we operated 12 months ago and that is a good thing. The way software projects provide support today is different to when this link was last discussed and today bugs are just one aspect of how support is managed. Today we have project specific issue tracking so linking to a single "bugs" page is not easy and a bit dated. Are links in the code worth the hassle? Do we actually think someone reading the code and finding a bug will need a link in the code to raise it? I don't think they do and these links seem to have become a hassle to maintain. -- View it on GitLab: https://gitlab.rtems.org/rtems/websites/www.rtems.org/-/issues/7#note_119092 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
