On 5/13/25 02:22, Tobias Burnus wrote:
[snip]
How about the attached patch? With it, running
./contrib/gcc-changelog/git_update_version.py \
--suffix '.omp' -c \
--exclude-branch=origin/releases/gcc-15 \
--last-commit=0b76b58a5875d519f95a5af661fb64e42a42ed8e
works where --last-commit could be, e.g.,
git log -1 --pretty=format:%H --grep "ChangeLog.omp Bump"
This could be wrapped in some script to (e.g. committed to this
the branch of interest) to handle the arguments and, possibly,
commit - with the possibility to skip commits if only
DATESTAMP<suffix> has changed.
This could then be run manually - or as someone's cronjob.
* * *
What do you - and anyone else - think about this approach?
Or about the original one? Or has yet another good alternative
or additional idea?
Update: after a few rounds of internal discussion, we've decided to use
Tobias's patch committed to the branch only in combination with a
wrapper script to run it locally with the right arguments and added
sanity-checking.
So, the devel/omp/gcc-15 branch is now populated and has the
auto-generated ChangeLog.omp files. :-)
-Sandra
