This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch zack/explicit-bzero in repository glibc.
discards a4eb2c4 Add a test for explicit_bzero not getting optimized out. discards 77d8b5d Use explicit_bzero where appropriate discards 52fa397 Add fortification support for explicit_bzero. discards f97024c New string function explicit_bzero (from OpenBSD). discards 175b79d Add tests for fortification of bcopy and bzero. adds 6f9d4f5 Fix incorrect double-checked locking related to _res_hconf.in [...] new d3bf0ba Add tests for fortification of bcopy and bzero. new 0b79bf3 New string function explicit_bzero (from OpenBSD). new bedc31b Add fortification support for explicit_bzero. new 3b9131a Use explicit_bzero where appropriate new 4d7aa37 Add a test for explicit_bzero not getting optimized out.
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 (a4eb2c4) \ N -- N -- N refs/heads/zack/explicit-bzero (4d7aa37)
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 5 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 | 13 +++++++++++++ nscd/aicache.c | 3 +-- nss/getXXbyYY_r.c | 3 +-- resolv/res_hconf.c | 3 ++- resolv/res_hconf.h | 9 +++++++++ sysdeps/posix/getaddrinfo.c | 3 +-- 6 files changed, 27 insertions(+), 7 deletions(-)