Chris Johns commented on a discussion: https://gitlab.rtems.org/administration/gitlab/-/issues/63#note_108506 I consider every file in a release as controlled. I never considered anyone would edit them. Yes you are right these links are wrong but there are many places around the net that will reference git . rtrems . org (written this way to not make another) we cannot erase. A release is a snapshot of RTEMS taken at the point of release and things will be wrong after a period of time. Consider https://ftp.rtems.org/pub/rtems/releases/4.10/4.10.2/ and: ``` The list of PRs is in the file PRs-closed-4.10.2 and in the RTEMS Wiki at: http://www.rtems.org/wiki/index.php/4.10_Release_Notes#Release_4.10.2_Changes Some of the enhancements included between the 4.9 and 4.10 release series are listed at: http://www.rtems.org/wiki/index.php/4.10_Release_Notes ``` and that is ignoring the references to RPMs (ahhh) in the next section. The last 4.10, 4.11 and 5 releases now have a file that will not match the release repo's release branch sources used to create those release _and_ those branches will not be able to recreate those releases until I update them. As I said we should make new dot releases to solve this problem. I appreciate what you are wanting to do but is this a deep deep well of problems. Maybe it is best to let sleeping dogs lie? -- View it on GitLab: https://gitlab.rtems.org/administration/gitlab/-/issues/63#note_108506 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
