From d94d6060488da23db738078541e4b08a743f763c Mon Sep 17 00:00:00 2001
From: Xi Ruoyao <xry111@xry111.site>
Date: Fri, 17 Feb 2023 15:36:40 +0800
Subject: [PATCH] packages: Mention Glibc stable branch in its package info

See the discussion at
https://sourceware.org/pipermail/libc-alpha/2023-February/145672.html.
---
 chapter03/packages.xml | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/chapter03/packages.xml b/chapter03/packages.xml
index d82e0b4c4..92d44afaf 100644
--- a/chapter03/packages.xml
+++ b/chapter03/packages.xml
@@ -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>