This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch topic/pipe in repository newlib.
discards f5a334d0a Cygwin: pipe: Restore blocking mode for cygwin process at startup. discards efcfc317f Cygwin: Document that the pipe_byte option is now set by default discards f08e7be0a Cygwin: fhandler_pipe::raw_read: minor code cleanup discards 3640430f3 Cygwin: pipe: Adopt FILE_SYNCHRONOUS_IO_NONALERT flag for read pipe. adds b959a5432 Cygwin: Correct the release notes 3.3.3. new 8c1bbf2f2 Cygwin: pipe: Suppress unnecessary set_pipe_non_blocking() call. new 9ba44c7b1 Cygwin: pipe: Adopt FILE_SYNCHRONOUS_IO_NONALERT flag for read pipe. new 13481c1eb Cygwin: fhandler_pipe::raw_read: minor code cleanup new dba679b2c Cygwin: Document that the pipe_byte option is now set by default new 54d07d394 Cygwin: pipe: Restore blocking mode for cygwin process at startup.
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 (f5a334d0a) \ N -- N -- N refs/heads/topic/pipe (54d07d394)
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 5 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/release/3.3.3 | 4 ++++ winsup/cygwin/spawn.cc | 9 ++++++--- 2 files changed, 10 insertions(+), 3 deletions(-)