diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2025-04-25 10:23:15 +0200 |
|---|---|---|
| committer | Jakub Jelinek <jakub@gcc.gnu.org> | 2025-04-25 10:23:15 +0200 |
| commit | fef3a3c8b5d35c7a8eeae67f95a264a90120dd29 (patch) | |
| tree | f11d50efe37e948e046329c3987cef753fb93ecf | |
| parent | 865d0f23d2ba08b3b6df6066e7dc5e807a14f5fa (diff) | |
| download | gcc-fef3a3c8b5d35c7a8eeae67f95a264a90120dd29.zip gcc-fef3a3c8b5d35c7a8eeae67f95a264a90120dd29.tar.gz gcc-fef3a3c8b5d35c7a8eeae67f95a264a90120dd29.tar.bz2 | |
Adjust gcc_release for id href web transformations
We now have some script which transforms e.g.
<h2 id="15.1">GCC 15.1</h2>
line in gcc-15/changes.html to
<h2 id="15.1"><a href="#15.1">GCC 15.1</a></h2>
This unfortunately breaks the gcc_release script, which looks for
GCC 15.1 appearing in gennews after optional blanks from the start of
the line in the NEWS file, which is no longer the case, there is
[129]GCC 15.1
or something like that with an URL later on
129. https://gcc.gnu.org/gcc-15/changes.html#15.1
The following patch handles this.
2025-04-25 Jakub Jelinek <jakub@redhat.com>
* gcc_release: Allow optional \[[0-9]+\] before GCC major.minor
in the NEWS file.
| -rwxr-xr-x | maintainer-scripts/gcc_release | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/maintainer-scripts/gcc_release b/maintainer-scripts/gcc_release index 2ead4a7..c7af3fd 100755 --- a/maintainer-scripts/gcc_release +++ b/maintainer-scripts/gcc_release @@ -141,7 +141,7 @@ build_sources() { "in gcc-${RELEASE_MAJOR}/index.html" sed -n -e "/^${thischanges}/,/^${previndex}/p" NEWS |\ - grep -q "^[[:blank:]]*GCC ${RELEASE_MAJOR}.${RELEASE_MINOR}" ||\ + grep -q "^[[:blank:]]*\(\[[0-9]\{1,\}\][[:blank:]]*\)\{0,1\}GCC ${RELEASE_MAJOR}.${RELEASE_MINOR}" ||\ error "GCC ${RELEASE_MAJOR}.${RELEASE_MINOR} not mentioned "\ "in gcc-${RELEASE_MAJOR}/changes.html" |