aboutsummaryrefslogtreecommitdiff
path: root/winsup/cygwin/how-vfork-works.txt
diff options
context:
space:
mode:
Diffstat (limited to 'winsup/cygwin/how-vfork-works.txt')
-rw-r--r--winsup/cygwin/how-vfork-works.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/winsup/cygwin/how-vfork-works.txt b/winsup/cygwin/how-vfork-works.txt
index 7148366..f249dab 100644
--- a/winsup/cygwin/how-vfork-works.txt
+++ b/winsup/cygwin/how-vfork-works.txt
@@ -28,8 +28,8 @@ the result of a vfork and closes the extra file handles.
This all relies on the fact that the child in a vfork call can affect
just about everything in the parent except for the parent's fds.
-The assumption is that a vfork is always just used as a method for
-starting a program.
+The assumption is that a vfork is always just used as a method for
+starting a program.
The assumption is also that all of this is much faster than the
slow method that cygwin uses to implement fork().