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 7ea1e10 Use explicit_bzero where appropriate discards b7f5628 Add fortification and inline optimization of explicit_bzero. discards d3f5d55 New string function explicit_bzero (from OpenBSD). new 9533ed6 New string function explicit_bzero (from OpenBSD). new 4546815 Add fortification and inline optimization of explicit_bzero. new 337e8f5 Use explicit_bzero where appropriate
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 (7ea1e10) \ N -- N -- N refs/heads/zack/explicit-bzero (337e8f5)
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: manual/string.texi | 99 +++++++++++++++++++++++++++++++++--------------------- 1 file changed, 61 insertions(+), 38 deletions(-)