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 f3827d6 malloc: Implement heap protector discards c33e430 Generate additional secret keys for the heap protector discards b96a747 crypt: Use internal names for the SHA-2 block functions adds 6b1df8b i386: Support CFLAGS which imply -fno-omit-frame-pointer [BZ #20729] new 3111495 crypt: Use internal names for the SHA-2 block functions new 09fa752 Generate additional secret keys for the heap protector new 9b685f9 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 (f3827d6) \ N -- N -- N refs/heads/fw/heap-protector (9b685f9)
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: ChangeLog | 24 ++++++++++++++++++ sysdeps/unix/sysv/linux/i386/Makefile | 47 ++++++++++++++++++++++++++--------- 2 files changed, 59 insertions(+), 12 deletions(-)