Gerald Pfeifer <ger...@pfeifer.com> writes: > On Wed, 12 Feb 2025, Sam James wrote: >> Suggested by Andrew Pinski. I think it makes sense to have it in here >> even if perhaps a bit verbose, because we really try to tell bug >> reporters to read the page properly. > > Makes sense. > >> This could also be a table. > > I'm not sure how a table would look like? (Genuinely, if you feel it'd be > better happy to have a look.)
I wasn't sure if maybe a "long bulletpoint list" was an antipattern, and then wondered about maybe "version/changes/porting to" as columns, but on reflection, it's overkill and let's not worry about it. > >> +GCC maintains a 'Porting to' resource for new versions of the compiler: > > How about skipping "of the compiler" (not the least since it's a set of > compilers ;-) and then something like > > "...new version: GCC 15 | GCC 14 | GCC 13 | ..." > > (or with commas or something along these lines)? ACK. > >> + <li><a href="https://gcc.gnu.org/gcc-15/porting_to.html";>GCC 15</a></li> > > Can you please make all these links relative, such as > ../gcc-15/porting_to.html ? ACK. > > Fine with these changes. > > Can you please also enhance the documentation for our release managers? > Probably branching.html (over releasing HTML since some distros give new > GCC versions a spin before the first release in the series). Will do -- thank you for the helpful comments and the quick review! > > Thank you, > Gerald thanks, sam
