This is an automated email from the git hooks/post-receive script.

unknown user pushed a change to branch fw/heap-protector in repository glibc.

discards 1488185 malloc: Implement heap protector discards 37a0a90 Generate additional secret keys for the heap protector discards e1afae2 sysmalloc: Initialize previous size field of mmaped chunks discards 41bc6bb malloc: Use accessors for chunk metadata access new d733d11 malloc: Use accessors for chunk metadata access new 95d70ee sysmalloc: Initialize previous size field of mmaped chunks new 5940351 Generate additional secret keys for the heap protector new 9b676a0 malloc: Implement heap protector

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 (1488185) \ N -- N -- N refs/heads/fw/heap-protector (9b676a0)

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 4 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: ChangeLog | 37 +++++++++++++++++++++++++++++++++++++ malloc/arena.c | 3 +-- 2 files changed, 38 insertions(+), 2 deletions(-)