Glibc tests occansionally fail due to a timeout because:
1. The hardware is slower than the developers expected.
2. Some tests use multiple or even all CPU cores internally, for e.g.
with 8 active CPU cores we may end up running 8 tests (due to -j8)
each of them uses 8 cores in the worst case, resulting a severe
congestion.
Let's change our policy to match other "rolling release" distros and
ease the procedure to fix Glibc security vulnerabilities.
Squashed the commits in xry111/update-glibc branch to keep the history
clean.
Add more rationale about --enable-stack-protector, and remove the stale explanation of --with-headers
Update upstream fixes patch
To include fixes for CVE-2023-6246, CVE-2023-6779, and CVE-2023-6780.
Don't use dummy.c for glibc sanity check in chap 5
grub: update description for grub-glue-efi
python: supress "failed to check new pip version" or "a new pip version is available" warnings
parition: mention EFI system partition
Remove all non header files in linux headers
groff: remove -j1
gcc-pass2: remove unnecessary --enable-initfini-array option
