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

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

discards f85022603 Cygwin: fhandler/null.cc: remove redundant includes discards 07cb0caf3 Cygwin: update the "dirs" variable in Makefile.am discards a5fd2a3c1 Cygwin: Reorganize cygwin source dir new 1e428bee1 Cygwin: mount_info::get_mounts_here: alloc temp mountpoint in [...] new 007e23d63 Cygwin: Reorganize cygwin source dir new 1213f7bf1 Cygwin: update the "dirs" variable in Makefile.am new 4d6c88e03 Cygwin: fhandler/null.cc: remove redundant includes

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 (f85022603) \ N -- N -- N refs/heads/topic/split_source_dir (4d6c88e03)

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: winsup/cygwin/mount.cc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)