On Tue, 21 Nov 2023, Tobias Burnus wrote: > On 21.11.23 14:57, David Malcolm wrote: > > On Tue, 2023-11-21 at 02:09 +0100, Hans-Peter Nilsson wrote: > > > Sorry for barging in though I did try finding the relevant > > > discussion, but is committing this generated stuff necessary? > > > Is it because we don't want to depend on Python being > > > present at build time? > > Partly, yes, [...] > > I wonder how to ensure that this remains up to date. Should there be an > item at > > https://gcc.gnu.org/branching.html and/or > https://gcc.gnu.org/releasing.html similar to the .pot generation?
My suggestion earlier in the discussion was that it should be added to the post-commit CI discussed starting at <https://gcc.gnu.org/pipermail/gcc/2023-November/242835.html> (I think that CI is now in operation). These are generated files that ought to be kept up to date with each commit that affects .opt files, unlike the .pot files where the expectation is that they should be up to date for releases and updated from time to time at other times for submission to the TP. -- Joseph S. Myers jos...@codesourcery.com
