This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch topic/shared_arch_headers in repository newlib.
discards cbbadbfb3 Add build mechanism to share common header files between machines new 3835c015d Add build mechanism to share common header files between machines new e8e95bf64 configure.host: define shared ix86 and x86_64 directory new 718f39554 fenv: add missing declarations to x86 fenv.h new a0d06f6c5 fenv: Move shared x86 sys/fenv.h from x86_64 to shared_x86 new c06e30d3d fenv: move shared x86 fenv.c to libm/machine/shared_x86 new 7803e212a fenv: drop Cygwin-specific implementation in favor of newlib code new 3b79d7e1c Cygwin: don't call _feinitialise from _dll_crt0
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 (cbbadbfb3) \ N -- N -- N refs/heads/topic/shared_arch_headers (3b79d7e1c)
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 7 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: