No description
Find a file
2024-03-07 16:03:52 +08:00
0083-CVE-2023-4527.patch fix CVE-2023-4527, CVE-2023-4806, CVE-2023-5156, CVE-2023-4911 2023-10-04 10:28:17 +08:00
0084-CVE-2023-4806.patch fix CVE-2023-4527, CVE-2023-4806, CVE-2023-5156, CVE-2023-4911 2023-10-04 10:28:17 +08:00
0085-CVE-2023-5156.patch fix CVE-2023-4527, CVE-2023-4806, CVE-2023-5156, CVE-2023-4911 2023-10-04 10:28:17 +08:00
0087-CVE-2023-6246.patch fix CVE-2023-6246, CVE-2023-6779, and CVE-2023-6780 2024-02-01 14:13:28 +08:00
0088-CVE-2023-6779.patch fix CVE-2023-6246, CVE-2023-6779, and CVE-2023-6780 2024-02-01 14:13:28 +08:00
0089-CVE-2023-6780.patch fix CVE-2023-6246, CVE-2023-6779, and CVE-2023-6780 2024-02-01 14:13:28 +08:00
1086-CVE-2023-4911.patch update to 2.38 2024-03-07 16:03:52 +08:00
bench.mk init from upstream 2.35 2022-03-03 20:05:59 +08:00
glibc-2.38.tar.xz update to 2.38 2024-03-07 16:03:52 +08:00
glibc-bench-compare init from upstream 2.35 2022-03-03 20:05:59 +08:00
glibc-cs-path.patch init from upstream 2.35 2022-03-03 20:05:59 +08:00
glibc-deprecated-selinux-makedb.patch init from upstream 2.35 2022-03-03 20:05:59 +08:00
glibc-fix-newlocale-error-return.patch init from upstream 2.35 2022-03-03 20:05:59 +08:00
glibc-gb18030-2022-bug30243.patch Add patch for gb18030-2022 from upstream bug#30243 2023-08-15 17:53:42 +08:00
glibc-no-archive-for-localedef.patch init from upstream 2.35 2022-03-03 20:05:59 +08:00
glibc-nscd-add-syslog-target-dependency.patch init from upstream 2.35 2022-03-03 20:05:59 +08:00
glibc-place-info-into-Libraries-category.patch init from upstream 2.35 2022-03-03 20:05:59 +08:00
glibc-python3.patch update to 2.38 2024-03-07 16:03:52 +08:00
glibc.spec update to 2.38 2024-03-07 16:03:52 +08:00
langpacklist Add patch for gb18030-2022 from upstream bug#30243 2023-08-15 17:53:42 +08:00
parse-SUPPORTED.py init from upstream 2.35 2022-03-03 20:05:59 +08:00
README.md init for Anolis OS 23 2022-02-22 14:27:07 +08:00
wrap-find-debuginfo.sh init from upstream 2.35 2022-03-03 20:05:59 +08:00

Anolis OS

代码仓库说明

分支说明

进行代码开发工作时,请注意选择当前版本对应的分支

  • aX分支为对应大版本的主分支,如a8分支对应当前最新版本
  • aX.Y分支为对应小版本的维护分支如a8.2分支对应8.2版本

开发流程

  1. 首先fork目标分支到自己的namespace
  2. 在自己的fork分支上做出修改
  3. 向对应的仓库中提交merge request源分支为fork分支