This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch hjl/pr21120/2.25 in repository glibc.
discards 42dbed7a84 configure: Suppress expected compiler error message discards 32a06064cd Make copy of <bits/std_abs.h> from GCC 7 [BZ #21573] discards 6ad06690d7 i386: Increase MALLOC_ALIGNMENT to 16 [BZ #21120] new 4ed5070c82 Make copy of <bits/std_abs.h> from GCC 7 [BZ #21573] new 594827f3f3 configure: Suppress expected compiler error message new c1ff8a0bf9 i386: Increase MALLOC_ALIGNMENT to 16 [BZ #21120]
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (42dbed7a84) \ N -- N -- N refs/heads/hjl/pr21120/2.25 (c1ff8a0bf9)
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: malloc/malloc-internal.h | 10 ---------- sysdeps/generic/malloc-alignment.h | 9 ++++++++- 2 files changed, 8 insertions(+), 11 deletions(-)