After this, patch order follows commit order. As a result,
some early patches get reordered from
Patch4: glibc-fedora-linux-tcsetattr.patch
Patch8: glibc-fedora-manual-dircategory.patch
Patch9: glibc-rh827510.patch
Patch13: glibc-fedora-localedata-rh61908.patch
Patch17: glibc-cs-path.patch
Patch23: glibc-python3.patch
Patch24: glibc-upstream-2.39-1.patch
to:
Patch1: glibc-rh827510.patch
Patch2: glibc-fedora-linux-tcsetattr.patch
Patch3: glibc-fedora-localedata-rh61908.patch
Patch4: glibc-fedora-manual-dircategory.patch
Patch5: glibc-cs-path.patch
Patch6: glibc-python3.patch
Patch7: glibc-upstream-2.39-1.patch
This still produces the same tree, so the reordering is harmless.
Resolves: RHEL-111490
Parent: 92dfd986b2
Patch-Git-Version: 1
RPM-Version: 2.39
RPM-Release: 60%{?dist}
RPM-Changelog-Stop: yes
