This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch azanella/qsort-refactor in repository glibc.
discards 47500d559b stdlib: Optimization qsort{_r} swap implementation discards 9dda5ba3a8 stdlib: Remove use of mergesort on qsort discards 68133fe423 benchtests: Add bench-qsort discards 11e3dbc464 stdlib: Add more qsort{_r} coverage discards 5f06b0b6f7 Fix discards a2d0969a09 support: Add Mersenne Twister pseudo-random number generator new 67d73eff76 support: Add pseudo-random number generator interface new 55365d62b7 stdlib: Add more qsort{_r} coverage new be32755802 benchtests: Add bench-qsort new 324cef4857 stdlib: Remove use of mergesort on qsort new 71ed300d4b stdlib: Optimization qsort{_r} swap implementation new f425f5ac83 stdlib: Remove undefined behavior from qsort implementation
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 (47500d559b) \ N -- N -- N refs/heads/azanella/qsort-refactor (f425f5ac83)
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 6 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: stdlib/qsort.c | 208 ++----------------------------------- stdlib/{qsort.c => qsort_common.c} | 142 ++++++------------------- 2 files changed, 39 insertions(+), 311 deletions(-) copy stdlib/{qsort.c => qsort_common.c} (65%)