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

unknown user pushed a change to branch fw/bug25097 in repository glibc.

discards 0b7470af80 Redefine _IO_iconv_t to store a single gconv step pointer [B [...] discards 51ac7d6bf2 slotinfo in struct dtv_slotinfo_list should be flexible arra [...] discards 6d241445b4 Avoid zero-length array at the end of struct link_map [BZ #25097] discards 7c0aae0bb3 Introduce link_map_audit_state accessor function discards 2cec33e197 Properly initialize audit cookie for the dynamic loader [BZ #25157] new 05efd60143 Properly initialize audit cookie for the dynamic loader [BZ #25157] new b1c595cec0 Introduce link_map_audit_state accessor function new 6a77162141 Avoid zero-length array at the end of struct link_map [BZ #25097] new 7591046cb1 slotinfo in struct dtv_slotinfo_list should be flexible arra [...] new 96ab757f9c Redefine _IO_iconv_t to store a single gconv step pointer [B [...]

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 (0b7470af80) \ N -- N -- N refs/heads/fw/bug25097 (96ab757f9c)

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: