packages: Mention Glibc stable branch in its package info

See the discussion at
https://sourceware.org/pipermail/libc-alpha/2023-February/145672.html.
This commit is contained in:
Xi Ruoyao 2023-02-17 15:36:40 +08:00
parent ce779ec8c1
commit d94d606048
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3

View File

@ -270,6 +270,20 @@
<para>Home page: <ulink url="&glibc-home;"/></para>
<para>Download: <ulink url="&glibc-url;"/></para>
<para>MD5 sum: <literal>&glibc-md5;</literal></para>
<note>
<para>
The Glibc developers maintain a
<ulink url='https://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/release/&glibc-version;/master'>Git
branch</ulink> containing patches considered worthy for
Glibc-&glibc-version; but unfortunately developed after
Glibc-&glibc-version; release. The LFS editors will issue a
security advisory if any security fix is added into the branch,
but no actions will be taken for other newly added patches. You
may review the patches yourself and incorporate some patches if
you consider them important.
</para>
</note>
</listitem>
</varlistentry>