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

unknown user pushed a change to branch topic/serial_io in repository newlib.

discards 8c58d00f9 Cygwin: serial: revamp overlapped IO in read and select discards 8288871fd Cygwin: serial: read: revamp raw_read, change vmin_ and vtime [...] discards f69f6b512 Cygwin: serial: select: simplify peek_serial new 4ad9ba42f Fix modf/f for NaN input new 213e16af0 Cygwin: serial: select: simplify peek_serial new 23db8962d Cygwin: serial: read: revamp raw_read, change vmin_ and vtime [...] new 2e8dab58f Cygwin: serial: revamp overlapped IO in read and select

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 (8c58d00f9) \ N -- N -- N refs/heads/topic/serial_io (2e8dab58f)

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 4 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: newlib/libm/common/s_modf.c | 1 + newlib/libm/common/sf_modf.c | 1 + 2 files changed, 2 insertions(+)